Problem with restart ImageJ-something related to Java

[nkxhm]

Hi Guys,
I met some problem with imageJ startup.  When I close imageJ and want to
open it for the second time, I always fail. If I terminated the process
named jawaw.exe, then I can startup imageJ. It is not convenient. Anybody
met this before?
Many thanks!

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

[Philip Ershler]

I've got the opposite problem on OS X. I assume your problem is with windows.  When I first try to start ImageJ after a reboot, ImageJ spends about a minute trying to start. Then after force quitting the app, it will start immediately thereafter until such time as I shut down the machine and restart it. I also believe it's tied up with Java.

Phil

On Apr 24, 2013, at 9:18 PM, Huiming Xia <[hidden email]> wrote:

> Hi Guys,
> I met some problem with imageJ startup.  When I close imageJ and want to
> open it for the second time, I always fail. If I terminated the process
> named jawaw.exe, then I can startup imageJ. It is not convenient. Anybody
> met this before?
> Many thanks!
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

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

[nkxhm]

That is interesting. Yes, I have 64bit windows 7 and java. I have no
problem with another computer with 32bit windows 7. Have no idea what is
going on.


On Wed, Apr 24, 2013 at 11:49 PM, Philip Ershler <[hidden email]>wrote:

> I've got the opposite problem on OS X. I assume your problem is with
> windows.  When I first try to start ImageJ after a reboot, ImageJ spends
> about a minute trying to start. Then after force quitting the app, it will
> start immediately thereafter until such time as I shut down the machine and
> restart it. I also believe it's tied up with Java.
>
> Phil
>
> On Apr 24, 2013, at 9:18 PM, Huiming Xia <[hidden email]> wrote:
>
> > Hi Guys,
> > I met some problem with imageJ startup.  When I close imageJ and want to
> > open it for the second time, I always fail. If I terminated the process
> > named jawaw.exe, then I can startup imageJ. It is not convenient. Anybody
> > met this before?
> > Many thanks!
> >
> > --
> > ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html
>

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

[Michael Schmid]

Hi Phil,

the problem of slow Java start can be caused by the 'repair disk permissions' feature of the Mac Disk utility - actually it seems to be an outdated feature that is still present in 10.6.

I remember that I had the same problem after 'repair disk permissions' on 10.6.
If I recall correctly, the 'x' flag for some directories, i.e., 'search' permission for directories was missing.

By the way, there seems to be also a problem with Sophos Anti-Virus causing excessive delays starting Java.

Michael
________________________________________________________________
On Apr 25, 2013, at 05:49, Philip Ershler wrote:

> I've got the opposite problem on OS X. I assume your problem is with windows.  When I first try to start ImageJ after a reboot, ImageJ spends about a minute trying to start. Then after force quitting the app, it will start immediately thereafter until such time as I shut down the machine and restart it. I also believe it's tied up with Java.
>
> Phil

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

[Philip Ershler]

Hi Michael,
        Yes it was Sophos that was causing the problem. I had to uncheck "Scan inside archives and compressed files". Even though I had tried to put in an exclusion for ImageJ and ImageJ64, I still had problems. Now ImageJ (and my other Java based apps)  launch immediately.

Thanks for the heads up,

Phil

On Apr 25, 2013, at 7:51 AM, Michael Schmid <[hidden email]> wrote:

> Hi Phil,
>
> the problem of slow Java start can be caused by the 'repair disk permissions' feature of the Mac Disk utility - actually it seems to be an outdated feature that is still present in 10.6.
>
> I remember that I had the same problem after 'repair disk permissions' on 10.6.
> If I recall correctly, the 'x' flag for some directories, i.e., 'search' permission for directories was missing.
>
> By the way, there seems to be also a problem with Sophos Anti-Virus causing excessive delays starting Java.
>
> Michael
> ________________________________________________________________
> On Apr 25, 2013, at 05:49, Philip Ershler wrote:
>
>> I've got the opposite problem on OS X. I assume your problem is with windows.  When I first try to start ImageJ after a reboot, ImageJ spends about a minute trying to start. Then after force quitting the app, it will start immediately thereafter until such time as I shut down the machine and restart it. I also believe it's tied up with Java.
>>
>> Phil
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

Philip R. Ershler Ph.D.
University of Utah
Cardiovascular Research and Training Institute
95 South 2000 East
Salt Lake City, UT 84112-5000

phone: [phone]
alt ph: [phone]
fax: [phone]
e-mail: [hidden email]



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

[dscho]

Hi,

On Thu, 25 Apr 2013, Huiming Xia wrote:

> That is interesting. Yes, I have 64bit windows 7 and java. I have no
> problem with another computer with 32bit windows 7. Have no idea what is
> going on.

If you already have the new ImageJ-win64.exe, you can rename it to
'debug.exe' to debug the issue. If you do not have the new launcher yet,
you can download it from
http://jenkins.imagej.net/job/Windows-Fiji-launcher-with-icons/label=Windows/
into your ImageJ directory.

Ciao,
Johannes

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

[nkxhm]

That works! Really appreciate.

On Thursday, April 25, 2013, Johannes Schindelin wrote:

> Hi,
>
> On Thu, 25 Apr 2013, Huiming Xia wrote:
>
> > That is interesting. Yes, I have 64bit windows 7 and java. I have no
> > problem with another computer with 32bit windows 7. Have no idea what is
> > going on.
>
> If you already have the new ImageJ-win64.exe, you can rename it to
> 'debug.exe' to debug the issue. If you do not have the new launcher yet,
> you can download it from
>
> http://jenkins.imagej.net/job/Windows-Fiji-launcher-with-icons/label=Windows/
> into your ImageJ directory.
>
> Ciao,
> Johannes
>

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

[Philip Ershler]

And following up on the OS X starting up issue, my problem was definitely Sophos. Unchecking "Scan zip and other compressed files" solved my problem.

Thanks for the thread,

Phil  

On Apr 26, 2013, at 12:45 PM, Huiming Xia <[hidden email]> wrote:

> That works! Really appreciate.
>
> On Thursday, April 25, 2013, Johannes Schindelin wrote:
>
>> Hi,
>>
>> On Thu, 25 Apr 2013, Huiming Xia wrote:
>>
>>> That is interesting. Yes, I have 64bit windows 7 and java. I have no
>>> problem with another computer with 32bit windows 7. Have no idea what is
>>> going on.
>>
>> If you already have the new ImageJ-win64.exe, you can rename it to
>> 'debug.exe' to debug the issue. If you do not have the new launcher yet,
>> you can download it from
>>
>> http://jenkins.imagej.net/job/Windows-Fiji-launcher-with-icons/label=Windows/
>> into your ImageJ directory.
>>
>> Ciao,
>> Johannes
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

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