Posted by
dscho on
Jun 20, 2011; 4:54pm
URL: http://imagej.273.s1.nabble.com/changing-memory-allocation-using-Fiji-ImageJ-tp3684178p3684183.html
Hi Raymond,
On Mon, 20 Jun 2011, Raymond Coory wrote:
> > -----Original Message-----
> > From: Johannes Schindelin [mailto:
[hidden email]]
> > Sent: Friday, 10 June 2011 11:40 a.m.
> > To: Raymond Coory
>
> > this is your lucky day, because I did not miss your mail in spite of
> > not being Cc:ed. I wonder whether you like to have speakers talk to
> > you while looking at the audience instead of you.
I actually did not mean to imply that I like private mails better than
mails that say "Hi Johannes" but are not addressed to me. I deem it polite
to reply to the author of the mail and Cc: the list.
> > On Fri, 10 Jun 2011, Raymond Coory wrote:
> >
> > > I also found that changing the memory in Edit-Options-Memory &
> > > Threads had no effect. There is a file called jvm.cfg in the Fiji
> > > folder, which updated to the new memory, but Fiji didn't read it,
> > > even though it had just written to it. I created a new file,
> > > ImageJ.cfg. Fiji did honour the memory setting in this file, but
> > > won't write to it. So it's a case of mixed identity.
> >
> > It would be good to know whether your ImageJ was updated to the daily
> > build or some other version rather what is in the Fiji Updater. If
> > that is true, that would explain things.
>
> sorry for not replying earlier. I wanted to check my installation of
> Fiji.
>
> I downloaded a fresh installation file, and updated everything from the
> built in updater. The results when attempting to change memory are still
> the same as I described.
>
> I'm on Windows XP (maybe that is the bug...!)
The next steps are to verify that
- jvm.cfg has been written to in the Fiji.app/ directory,
- jvm.cfg contains text corresponding to the memory amount you wanted to
set,
- fiji, when called from the command line with --console, does not report
issues with failures to reserve heap size, and that
- fiji, when called from the command line with --console --dry-run, does
show the correct memory option (and does not try to override it later on
the command line)
For information how to run Fiji from the command line, please refer to
http://fiji.sc/Debugging_intro#Command_line_debuggingCiao,
Johannes