Re: How can I run ImageJ with Java 1.6 on my MacBook?
Posted by
ctrueden on
URL: http://imagej.273.s1.nabble.com/How-can-I-run-ImageJ-with-Java-1-6-on-my-MacBook-tp3691203p3691209.html
Hi Harry,
Hopefully, ImageJ64 will work for you. If not, it might be possible to use
32-bit Java 1.6 on Mac OS X 10.5, using the OpenJDK 6 port, but I haven't
tested it. Unfortunately, the documentation on how to do this is pretty
scattered and difficult, but in case you are interested here are some links:
Overview:
http://landonf.bikemonkey.org/2009/05/17Supposedly can be installed using MacPorts (package is "openjdk6"):
http://www.macports.org/Though apparently doesn't work on Snow Leopard at the moment:
http://trac.macports.org/ticket/20956I'd be interested to hear if anybody has tried this or manages to get it
working!
-Curtis
On Thu, Sep 10, 2009 at 12:29 PM, Wayne Rasband <
[hidden email]> wrote:
> > I have a MacBook running Mac OS X 10.5.8 with
> > 1 GB of RAM. I would like to use Jerek Sacha's
> > ij-plugins-toolkit, but they require Java 1.6.
> >
> > I have Java SE 1.6 64 bit on this Mac as well as Java 1.5,
> > but the ImageJ Installation page mentions ImageJ will only
> > use Java 1.6 if the machine has more than 2.5 GB RAM.
> >
> > So is there any way to convince my copy of ImageJ to
> > use Java 1.6 without stuffing more RAM into my MacBook?
>
> ImageJ for Mac OS X comes with two applications (launchers), ImageJ and
> ImageJ64. On Mac OS X 10.5 (Leopard), ImageJ uses a 32-bit version of Java
> 1.5 and ImageJ64 uses a 64-bit version of Java 1.6. On Mac OS X 10.6 (Snow
> Leopard), ImageJ uses a 32-bit version of Java 1.6 and ImageJ64 uses a
> 64-bit version of Java 1.6. ImageJ64 is much faster than ImageJ but it
> crashes more often and it is not able to run commands, such as File>Import>
> Using QuickTime, that use QuickTime for Java. Image64 does not required 2.5
> GB or RAM but it is able to use more than 1.8 GB if you have more than 2 GB
> installed.
>
> I did some benchmarking and found that the getPixel() method is ~4 times
> faster when running ImageJ64. It is as fast as directly accessing the pixel
> data, which means that Java 1.6 must be inlining the getPixel() method.
>
> -wayne
>