Posted by
dscho on
Jun 09, 2011; 7:14am
URL: http://imagej.273.s1.nabble.com/changing-memory-allocation-using-Fiji-ImageJ-tp3684178p3684180.html
Dear Susan,
On Wed, 8 Jun 2011, Susan Travers wrote:
> I believe that I lost the last message that you sent me yesterday
> regarding changing the memory allocation with Fiji. (sorry).
Heh, no need to be sorry. Furthermore, since I make a point of answering
to the mailing list, chances are that you can find my mail here:
http://news.gmane.org/gmane.comp.java.imagej> Anyway, I am really baffled by this. I see that the jvm.cfg file (which
> is in the same subdirectory as the fiji-win32.exe file) reflects the
> changes that I make by going into "options"/"memory", but those changes
> don't get reflected the next time I start Fiji-- it seems as if the
> program is deciding on how much memory to use, independent of any
> changes that I make.
Then it might be a good idea to start Fiji with --dry-run to see what
options are passed to Java and ImageJ, respectively. See
http://fiji.sc/Debugging_intro#Command_line_debuggingfor details how to start Fiji from the command line.
> (I am at least a little less confused than before, because I realized
> that I had a copy of image j that was totally unrelated to the Fiji
> version that I am using, so initially I was looking at the wrong config
> file; I have now deleted the plain ImageJ version).
>
> Not being able to change the memory is not too big a problem, but I
> would like to be able to figure this out. Thanks for pointing me in any
> likely direction.
>
> PS, the version info is ImageJA 1.45i Java 1.60_24 32-bit
Yep, that is up-to-date.
If worse comes to worst, you can always start Fiji from the command line
and specify an amount of RAM directly with the --mem=<amount> (where
<amount> is something like 1500m).
Ciao,
Johannes