⚠

NOTICE! This is a static HTML version of a legacy Fiji BugZilla bug.

The Fiji project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Bug 7 - memory significant smaller.
memory significant smaller.
Status: RESOLVED WONTFIX
Product: ImageJ
Classification: Unclassified
Component: Launcher
unspecified
Macintosh Mac OS
: P2 major
Assigned To: ImageJ Bugs Mailing List
Depends on:
Blocks:
 
Reported: 2008-06-23 19:26 CDT by aRnim Jenett
Modified: 2015-04-06 15:44 CDT
0 users

See Also:
Description aRnim Jenett 2008-06-23 19:26:53 CDT 
I don't exactly know, what youre doing in the background, but using Fiji "on the edge" of what is feasable on a 32bit tiger-mac I find me running in "out-of-memory"s quite oftenthe garbage collector than tells me, that I just have about 1.1GB of memory and that is easily used up by the data I am displaying - no room for processing anymore. 
I know tiger is not the latest MacOS, but a pretty common still. Can we - meaqning you - somehow overcome that? What about starting fiji itself in a different java instance than the starter. Thereby i should be able to get the whole chunk of 2GB java memory, not competing with the starter... just my user-opinion.
this is true for all fiji-versions i touched.
Comment 1 Johannes Schindelin 2008-11-06 19:21:15 CST 
Unfortunately, the issue is not the launcher.  It runs the process, but does not take all that much memory.  The issue is really the Java Virtual Machine, which cannot really use more than 2G (and often not even that) on 32-bit architectures.
Comment 2 Johannes Schindelin 2008-11-10 14:48:17 CST 
So I looked at the issues again, and it appears to me that we cannot do anything about the issue. Sorry!