Posted by
ctrueden on
Nov 17, 2015; 7:45pm
URL: http://imagej.273.s1.nabble.com/Memory-usage-in-WEKA-segmentation-tp5014961p5014963.html
Hi Ben,
> I've tried increasing the maximum memory in Edit>Options>Memory &
> Threads from the default 505MB to 1, 2, 4GB and more (running Win 8.1
> 64bit with 16GB RAM), but ImageJ never uses more than 505MB
I have seen other users describe this same problem a couple of times. But I
do not know why it happens. It would be great to troubleshoot and find the
answer, so that we can add it to the
http://imagej.net/Troubleshooting page.
You can try launching ImageJ from the command line:
http://imagej.net/Troubleshooting#Launching_ImageJ_from_the_consoleTry changing the memory allocation directly; e.g.:
C:\Users\me\Programs\Fiji.app\ImageJ-win64.exe -mx512m --
C:\Users\me\Programs\Fiji.app\ImageJ-win64.exe -mx1g --
C:\Users\me\Programs\Fiji.app\ImageJ-win64.exe -mx4g --
You can also use:
C:\Users\me\Programs\Fiji.app\ImageJ-win64.exe --dry-run --console
To get the full command line used by the ImageJ launcher. You can then
experiment with making changes to that command line as needed.
Lastly, you could give this Windows batch launcher a try:
*
https://raw.githubusercontent.com/imagej/imagej/master/bin/ImageJ.batLet us know how what you find out! Again, I would love to have a solution
for those people who occasionally encounter this issue.
Regards,
Curtis
On Tue, Nov 17, 2015 at 11:08 AM, ben_king <
[hidden email]> wrote:
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html