http://imagej.273.s1.nabble.com/Memory-usage-in-WEKA-segmentation-tp5014961p5014973.html
Awesome, so glad you figured it out. And glad to have another known culprit
for anyone else who might report this issue in the future.
> Problem solved - there was a system environment variable _JAVA_OPTIONS
> containing "-Xmx512m." I must have. I noticed it when I went to make an
> environment variable to try other javas.
>
> I changed the _JAVA_OPTIONS environment variable to -Xmx10g and then IJ
> loads with/uses upto 10g.
>
> Curiously, I tried deleting the environment variable and setting -Xmx256m
> in
> ImageJ.cfg, but IJ still uses over 256MB so I don't know what is limiting
> IJ
> memory usage without the environment variable. Maybe the system needs to
> restart for it to take effect.
>
> Thanks for all your help, Curtis!
>
>
>
> --
> View this message in context:
>
http://imagej.1557.x6.nabble.com/Memory-usage-in-WEKA-segmentation-tp5014961p5014972.html> Sent from the ImageJ mailing list archive at Nabble.com.
>
> --
> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>