Fiji will not restart

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Fiji will not restart

Yuekan Jiao-2
Hi

Frequently Fiji will not restart after it is quit by using the “X”
button on the title bar or “Quit” commend under "File" menu. It looks
that Fiji actually does not quit, I have to use Windows Task Manager
to force it to quit, then it can be restart.  I have the issue with
both 32-bit version on Windows XP professional and 64-bit version on
Windows 7. Is there a way to fix it?

Thanks

Yuekan

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not restart

dscho
Hi Yuekan,

On Thu, 21 Mar 2013, Yuekan Jiao wrote:

> Frequently Fiji will not restart after it is quit by using the “X”
> button on the title bar or “Quit” commend under "File" menu. It looks
> that Fiji actually does not quit, I have to use Windows Task Manager to
> force it to quit, then it can be restart.  I have the issue with both
> 32-bit version on Windows XP professional and 64-bit version on Windows
> 7. Is there a way to fix it?

Could you make a copy of ImageJ-win64.exe, rename it to debug.exe and
start the? It should give you quite a lot of output that I'd like to ask
you to copy & paste into a reply *as text* (i.e. not as .png or .jpg).

Ciao,
Johannes

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not restart

Yuekan Jiao-2
Hi Johannes,

I had a closer look at the issue, it happens when Fiji is quit after a
TrakEM2 project is created (even an empty project without loading
images - we used TrackEM2 to stitch images). If you look at Windows
Task Manager, when Fiji is quit, Fiji and TrakEM2 disappear in the
Applications, but ImageJ-win64.exe / ImageJ-win32.exe is still in the
Processes.

With the previously installed ImageJ-win64.exe / ImageJ-win32.exe, I
made the copy of debug.exe file, it did not output any text. I
downloaded and re-installed ImageJ-win64.exe on a Windows 7 computer,
the debug file outputs text attached.

Thank you.

Yuekan


On Thu, Mar 21, 2013 at 2:31 PM, Johannes Schindelin
<[hidden email]> wrote:

> Hi Yuekan,
>
> On Thu, 21 Mar 2013, Yuekan Jiao wrote:
>
>> Frequently Fiji will not restart after it is quit by using the “X”
>> button on the title bar or “Quit” commend under "File" menu. It looks
>> that Fiji actually does not quit, I have to use Windows Task Manager to
>> force it to quit, then it can be restart.  I have the issue with both
>> 32-bit version on Windows XP professional and 64-bit version on Windows
>> 7. Is there a way to fix it?
>
> Could you make a copy of ImageJ-win64.exe, rename it to debug.exe and
> start the? It should give you quite a lot of output that I'd like to ask
> you to copy & paste into a reply *as text* (i.e. not as .png or .jpg).
>
> Ciao,
> Johannes
--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html

Debug message.txt (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Fiji will not restart

dscho
Hi Yuekan,

On Fri, 22 Mar 2013, Yuekan Jiao wrote:

> I had a closer look at the issue, it happens when Fiji is quit after a
> TrakEM2 project is created (even an empty project without loading images
> - we used TrackEM2 to stitch images). If you look at Windows Task
> Manager, when Fiji is quit, Fiji and TrakEM2 disappear in the
> Applications, but ImageJ-win64.exe / ImageJ-win32.exe is still in the
> Processes.
>
> With the previously installed ImageJ-win64.exe / ImageJ-win32.exe, I
> made the copy of debug.exe file, it did not output any text. I
> downloaded and re-installed ImageJ-win64.exe on a Windows 7 computer,
> the debug file outputs text attached.

Thanks. There is nothing abnormal in that output. Could you install a JDK
from http://www.oracle.com/technetwork/java/javase/downloads/index.html,
call debug.exe with the --system option and call JDK's JVisualVM and make
a thread dump after closing the main window?

My hunch is that there is still a runaway thread that was not properly
terminated (TrakEM2 uses multi-threading extensively, and multi-threading
is an obnixiously hard thing to master).

Ciao,
Johannes

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