http://imagej.273.s1.nabble.com/Odd-annoying-behavior-of-Fiji-64-on-a-high-end-workstation-tp5008695p5008715.html
Yes, I was dearly hoping the bug is fixed now. Are you sure your ImageJ is
> Hi Stoyan,
>
> I'll save Johannes and Curtis a minute or two:
>
> This is a known bug, AKA "Fiji won't quit!", which is well reported here
> and (meant to be) fixed.
>
> Read this for more info:
>
>
http://imagej.net/2014-07-11_-_Fiji_won%27t_quit>
> Have a nice weekend,
>
> Michael
>
>
> On 12/07/14 16:28, Stoyan Pavlov wrote:
> > 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> >
>
> <
http://www.rvc.ac.uk>
>
> This message, together with any attachments, is intended for the stated
> addressee(s) only and may contain privileged or confidential information.
> Any views or opinions presented are solely those of the author and do not
> necessarily represent those of the Royal Veterinary College.
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>