Posted by
Wayne Rasband on
Sep 10, 2008; 2:57am
URL: http://imagej.273.s1.nabble.com/unexplainable-memory-limit-in-ImageJ64-tp3692745p3692746.html
On Sep 9, 2008, at 5:46 PM, Robert Dougherty wrote:
> Dear ImageJ people,
>
> I'm getting <Out of memory> errors at 653 MB in ImageJ64,
> regardless of the amount of memory assigned in Options/Memory &
> Threads. The patient is a MacBook Pro with 4 GB of memory running
> OS X 10.5.2. ImageJ version 1.4.1k, Java version 1.4.2_16. It
> does not seem to matter how I get to 653 MB: the same thing happens
> with a complicated plugin or just opening the mri-stack sample and
> scaling it up. The memory monitor shows only 35% used, or so. The
> problem is specific to ImageJ64. The 32-bit version of ImageJ
> works fine. I suspected a hardware problem because the memory
> expansion from 2 GB to 4 GB included breaking the little clips that
> retain the cards. (The proper way to disengage the clips is to
> spread them horizontally, not pry them up...) However, an extended
> hardware test revealed no problems. Any ideas?
ImageJ64 requires Java 1.5 or later, Mac OS X 10.5 and a 64-bit Intel
processor. Java 1.6, which is 64-bit only, is available via Software
Update, although it is is not made the default version of Java. To
make it the default, switch to "Java SE 6 (64-bit)" in /Applications/
Utilities/Java/Java Preferences.
> Another ImageJ64 puzzle is that Quicktime works on one MacBook
> pro, but not a seemingly identical other one when running
> ImageJ64. It works on both machines with regular ImageJ.
QuickTime for Java is not 64-bit compatible. The machine it is
working on is probably running 32-bit Java and the other one is
probably running 64-bit Java. The title of the Edit>Options>Memory &
Threads dialog box changes to "Memory (64-bit)" when ImageJ is
running on a 64-bit version of Java.
-wayne