Ticket #2034 (closed defect: moved)
Opened 2013-12-04T11:53:33-06:00
Last modified 2013-12-04T13:26:04-06:00
Launcher doesn't respect ImageJ.cfg memory
| Reported by: | hinerm | Owned by: | dscho |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | Build System | Version: | 2.0.0-beta-7 |
| Severity: | major | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: |
Description
On OSX, using an ImageJ.cfg in ImageJ.app/, with the line:
maxheap.mb = 384
the max memory is still being set to 3/4 available RAM. So this configuration file is not being properly respected by the launcher.
Attachments
Change History
comment:1 Changed 2013-12-04T12:32:49-06:00 by curtis
- Cc curtis removed
- Owner changed from curtis to dscho
- Status changed from new to assigned
comment:2 Changed 2013-12-04T12:42:21-06:00 by dscho
Do you have debug output somewhere? (Copy the launcher to debug -- still in Contents/MacOS/, and edit the Info.plist to call debug instead of ImageJ-tiger, then copy the output of Finder>Applications>Utilities>Console)
Changed 2013-12-04T13:22:22-06:00 by hinerm
- attachment debug.txt added
output of running renamed launcher to debug
comment:3 Changed 2013-12-04T13:26:04-06:00 by hinerm
dscho: I couldn't get these directions to work.
I tried copying both /Contents/MacOS/ImageJ-macosx and ImageJ-tiger to debug, and then changed the CFBundleExecutable value to "debug" in the Info.plist. But there was no debugging output, and nothing in Console.
The attached debug.txt is the logging output after copying ImageJ-tiger to debug and running it directly (after generating an ImageJ.cfg with a 384mb max heap).
comment:4 Changed 2014-05-01T16:32:40-05:00 by curtis
- Status changed from assigned to closed
- Resolution set to moved
I blame Johannes.