ImageJ crashes Windows 7 but not in safe mode

[Jeff Hardin]

Hi all,
In case anyone else see this behavior, here is a follow-up...

Nico Stuurman alerted me to differences in the application launcher platform on Windows for Fiji vs. ImageJ and MicroManager (see below). It turns out that my problem is not unique to ImageJ/M-M. It is an apparent bug in the 3d graphics acceleration under VMWare Fusion 5.0.2 and its interaction with Retina display Macbook Pros. Turning off 3d Acceleration fixes the problem...

Cheers,
Jeff
----------------------------------------
Jeff Hardin
Professor and Chair, Department of Zoology
Director, Biology Core Curriculum
University of Wisconsin
1117 W. Johnson St.
Madison, WI 53706
voice: [phone]
fax: [phone]
email: [hidden email]
web page: http://worms.zoology.wisc.edu

On Nov 14, 2012, at 1:12 AM, Nico Stuurman <[hidden email]> wrote:

> Hi Jeff,
>
> Somehow sounds like a problem with the launcher.  ImageJ uses a launcher written in Turbo Pascal.  Micro-Manager uses the same launcher code.  Fiji has its own launcher.  I don't know how to exchange the ImageJ and Fiji launchers (may not even be possible without changing many other things), but that experiment could nail it.
>
> Potentially, you could file a bug report with VMWare.
>
> Best,
>
> Nico
>
>
> On Nov 13, 2012, at 9:58 PM, Jeff Hardin wrote:
>
>> Dear Imagers,
>> I have a weird problem after migrating a VMWare Fusion 5 Windows virtual machine to a new Mac laptop running Mountain Lion (OS X 10.8). I know this is a highly specialized, but I thought I'd send in the symptoms.
>>
>> The Win7 virtual machine worked great in the past, and I could run ImageJ (with JRE) just fine. On the new Mac, however, ImageJ results in an unrecoverable crash of Windows. The main ImageJ window starts to appear, and then locks up the machine. I can reboot into Safe Mode with Networking, and ImageJ runs fine. Then if I restart Winy normally, I can run ImageJ successfully. After another restart, however, the machine will always crash again.
>>
>> Deleting ImageJ and reinstalling doesn't help. Similar irretrievable crashing occur with MicroManager, which relies on ImageJ. Fiji (32-bit), on the other hand, runs fine. Moreover, I can run ImageJ using VMWare Fusion under XP on the same Mac.
>>
>> Anyone up for a challenge? Help with troubleshooting this weird behavior would be greatly appreciated!
>>
>> Cheers,
>> Jeff

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

[Rasband, Wayne (NIH/NIMH) [E]]

On Nov 14, 2012, at 12:42 PM, Jeff Hardin wrote:

> Hi all,
> In case anyone else see this behavior, here is a follow-up...
>
> Nico Stuurman alerted me to differences in the application launcher platform on Windows for Fiji vs. ImageJ and MicroManager (see below). It turns out that my problem is not unique to ImageJ/M-M. It is an apparent bug in the 3d graphics acceleration under VMWare Fusion 5.0.2 and its interaction with Retina display Macbook Pros. Turning off 3d Acceleration fixes the problem...

You could also try adding the "-Dsun.java2d.noddraw=true" option to the ImageJ.cfg file in the ImageJ folder. The three line ImageJ.cfg file will look something like this:
   .
   jre\bin\javaw.exe
   -Xmx700m -cp ij.jar -Dsun.java2d.noddraw=true ij.ImageJ

The Fiji launcher sets this option by default. Or use the nVidia Fix plugin at

    http://imagej.nih.gov/ij/plugins/nvidia-fix/index.html

which adds "-Dsun.java2d.noddraw=true" to ImageJ.cfg. If there is a problem, delete ImageJ.cfg and it will be recreated the next time you run ImageJ.

-wayne

> On Nov 14, 2012, at 1:12 AM, Nico Stuurman <[hidden email]> wrote:
>
>> Hi Jeff,
>>
>> Somehow sounds like a problem with the launcher.  ImageJ uses a launcher written in Turbo Pascal.  Micro-Manager uses the same launcher code.  Fiji has its own launcher.  I don't know how to exchange the ImageJ and Fiji launchers (may not even be possible without changing many other things), but that experiment could nail it.
>>
>> Potentially, you could file a bug report with VMWare.
>>
>> Best,
>>
>> Nico
>>
>>
>> On Nov 13, 2012, at 9:58 PM, Jeff Hardin wrote:
>>
>>> Dear Imagers,
>>> I have a weird problem after migrating a VMWare Fusion 5 Windows virtual machine to a new Mac laptop running Mountain Lion (OS X 10.8). I know this is a highly specialized, but I thought I'd send in the symptoms.
>>>
>>> The Win7 virtual machine worked great in the past, and I could run ImageJ (with JRE) just fine. On the new Mac, however, ImageJ results in an unrecoverable crash of Windows. The main ImageJ window starts to appear, and then locks up the machine. I can reboot into Safe Mode with Networking, and ImageJ runs fine. Then if I restart Winy normally, I can run ImageJ successfully. After another restart, however, the machine will always crash again.
>>>
>>> Deleting ImageJ and reinstalling doesn't help. Similar irretrievable crashing occur with MicroManager, which relies on ImageJ. Fiji (32-bit), on the other hand, runs fine. Moreover, I can run ImageJ using VMWare Fusion under XP on the same Mac.
>>>
>>> Anyone up for a challenge? Help with troubleshooting this weird behavior would be greatly appreciated!
>>>
>>> Cheers,
>>> Jeff

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