NOTICE! This is a static HTML version of a legacy ImageJ Trac ticket.

The ImageJ project now uses GitHub Issues for issue tracking.

Please file all new issues there.

Ticket #1044 (closed task: fixed)

Opened 2012-03-02T09:13:18-06:00

Last modified 2012-04-29T17:47:27-05:00

Make IJ2 respect user specified memory limits

Reported by: bdezonia Owned by: dscho
Priority: major Milestone: imagej2-b3-headless
Component: Other Version:
Severity: serious Keywords:
Cc: Blocked By:


IJ2 has an option (in OptionsMemoryAndThreads) specifying how much ram IJ2 should use. This setting currently has no effect. Make some code that listens for OptionsEvents, sees that the memory setting has changed, and updates the launcher script (or something) so that IJ2 tries to allocate that much ram appropriately.

Note that right now the About ImageJ2 image shows memory in use as a percentage of the user specified limit. Since that limit is not used people will have incorrect ideas about what limit is in place. They may report bugs thinking they have plenty of ram when in fact they are out.

Change History

comment:1 Changed 2012-03-02T09:29:34-06:00 by bdezonia

In e8e8b893a0ae2fb575f4488a2195d93fa67b9f07 fixed about dialog to more accurately report available memory. The second paragraph above is no longer an issue.

comment:2 Changed 2012-04-29T17:47:27-05:00 by dscho

  • Status changed from new to closed
  • Resolution set to fixed

Barry implemented the config file writing in 0ff1796b2d0b4b906778069c09170b96abfd981e and in 021946ca6f4b5c5c7fe2922cea6606a02c86c54e the ImageJ launcher learnt to understand the new-style config file.