Posted by
Aryeh Weiss on
Jul 21, 2015; 3:59am
URL: http://imagej.273.s1.nabble.com/java-8-and-OSX-tp5013642p5013667.html
Thanks to all who have replied to my post. It is good to know that I
have company...
On 7/20/15 6:33 PM, Michael Ellis wrote:
> I too rely on plugins that require Java 8 (lne we build ourselves) and have also found some problems with ImageJ under Java 8 (slow image updates used to be a big problem). These problems seem to have been improving with ImageJ releases and also with Java 8 releases.
>
> I would make sure you have the latests Java 8 installed (some early versions had show stopping bugs which have since been fixed).
>
I have 1.8.0_51 (64 bit) downloaded two days ago.
> Beyond this all I wish to add is a note to anyone involved in ImageJ development that moving to newer JVM’s becomes increasingly important as the older JVMs become increasingly difficult to get support for on the Apple platform and also that anyone doing any development for plugins is increasingly likely to be tooled up to reply on Java 8.
>
To aid in this effort, I will try to find some pattern in these
problems. I run Fiji with ImageJ 1.50a20 (daily build) under OSX
10.10.4, 12GB (out of 16GB) assigned to Fiji, and Java 1.8.0_51.
So far, the biggest problem is indeed slow update, but more so, failure
to respond to certain actions in the ROI manger (actions which involve
some kind of update -- eg select ROI or show-all). Also, it can take a
really longtime for the menu to redisplay when selecting images (this is
probably OSX specific because it needs to update the menu every time a
different application or even a different image window is selected).
In is often hard to distinguish between a failure, or something that
will happen if one waits long enough.
I try to use the memory monitor to see if something is happening, but
that does not display anything.
In any case, for the ROI manager, I was able to save the ROI set, close
the ROI manager window, and then reload it. The reloaded ROI manager
worked ok for a while.
Closing and restarting Fiji temporarily resolves the problems.
Also , I am working with large images (about 15k x 15k pixels, 16 bit).
Hope this provides some clues...
> I understand that desire for backwards compatibility but there’s always going to be tradeoff!
>
> — Michael Ellis
Best regards,
--aryeh
--
Aryeh Weiss
Faculty of Engineering
Bar Ilan University
Ramat Gan 52900 Israel
Ph: 972-3-5317638
FAX: 972-3-7384051
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html