Odd/annoying behavior of Fiji 64 on a high end workstation

Posted by Stoyan Pavlov on Jul 12, 2014; 3:28pm
URL: http://imagej.273.s1.nabble.com/Odd-annoying-behavior-of-Fiji-64-on-a-high-end-workstation-tp5008695.html

Hello dear friends,
In our department we recently acquired a high end workstation for image
processing and analysis (16 core 3.2 Mhz, 64 Gbyte RAM). I downloaded
Fiji. I wanted to use the 64 bit version in order to be able to utilize the
enormous RAM of the workstation. Everything seems to work just fine. There
is however an annoying behavior (frankly I am not sure that the problem is
in Fiji): when I work with the program for a while and then I want to end
it, Fiji doesn't end when I quit it (neither using the x of the window or
the exit command in the menu) and I need to go and kill the Imagej-64
process through the task manager. Even more the associated Java32 process
must be killed too. And this leads me to another question: Isn't Fiji64
supposed to use java64 (i have both -32bit and 64bit installed on the
machine) , why does it start a Java32.exe instead?
Best wishes to all
Stoyan

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html