Hide Forgot
Description of problem: On a computer with 16 GB RAM, default memory limit of ImageJ is 768 MB. 683 MB in effect. Changing memory limit of ImageJ using built-in option menu of ImageJ fails with unhelpful message. Workaround is: increase memory limit using command line: imagej -x 12843 Version-Release number of selected component (if applicable): imagej-1.50-1.h.fc24.noarch How reproducible: 100% Steps to Reproduce: 1. $ sudo dnf install -y imagej 2. $ imagej 3. Edit -- Options -- Memory & Threads... 4. change 'Maximum memory' option and click on [OK] Actual results: Memory --- ImageJ is unable to change the memory limit. For more information, refer to the installation notes at http://imeji.nih.gov/ij/docs/install/ Current limit: 683 MB [OK] Expected results: Please, make the 'Edit -- Options -- Memory & Threads...' window usable for regular users. Message should be like in Windows: 'new value written to configuration file; please restart ImageJ to active it' Additional info: Please, change line 83 and line 89 of '/usr/bin/imagej' from : if (( $mem > $default_mem || $mem < $min_mem )) ; then mem=$default_mem ; fi to: if (( $mem < $default_mem || $mem < $min_mem )) ; then mem=$default_mem ; fi to increase the default memory limit to 2/3 of memory. Looking at '/usr/bin/imagej' more closely, it would be nice to follow XDG. https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html Unfortunately, in Xfce XDG_CONFIG_HOME and XDG_DATA_HOME are not set. Hence I am using their recommended replacements. I would change: ij_user_path="${HOME}/.imagej" to: ij_user_path="${HOME}/.config/imagej" (using replacement of XDG_CONFIG_HOME) I would change: ij_tmp="${HOME}/.imagej/tmp" to: ij_tmp="${HOME}/.local/share/imagej/tmp" (using replacement of XDG_DATA_HOME)
Thanks for reporting this problem. I"m a little reluctant to make such a large behaviour change in a Fedora-specific patch. Do you know whether this problem occurs in other distributions, or only on Fedora?
In Lubuntu 14.04 with ImageJ 1.48k it is the same behaviour. I assume all distributions are affected.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
reproducable on Fedora 26 with imagej-1.50-2.h.fc26.noarch
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I could change the 'Maximum memory' option using the ImageJ GUI with the latest upstream version 1.52a on Fedora 28 by downloading the ZIP file, extracting it and running: $ ./ImageJ Edit -- Options -- Memory & Threads... However the value is saved to the 'ImageJ.cfg' file next to the 'ImageJ' file. $ cat ImageJ.cfg . jre/bin/java -Xmx222m -cp ij.jar ij.ImageJ Where '222m' is 222 MB. If 'ImageJ.cfg' is read-only, i.e. installed to /usr/share/imagej, the problem from above is still present. If there is an option to read/write 'ImageJ.cfg' from/to the users home directory the memory allocation problem would be resolved. Unfortunately, I could not find such a setting.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.