Re: Memory usage in WEKA segmentation

Posted by ben_king on Nov 17, 2015; 10:25pm
URL: http://imagej.273.s1.nabble.com/Memory-usage-in-WEKA-segmentation-tp5014961p5014965.html

Curtis,

Running from the console didn't fix it but it did something. Here's what I have tried:

1. Ran from console with -mx*anything* flag, ImageJ loads with 494MB available memory and gives out of memory exception when it uses all 494MB

2. Ran from console with -Xmx*anything* or no flags, ImageJ loads with 505MB and uses up to 505MB

3. Put -Xmx256m flag in ImageJ.cfg file then ran ImageJ (either from console with no flags or by clicking icon), ImageJ loads and says 256MB available under Help->About ImageJ, but still uses up to 505MB (200%)

4. Put -Xmx1g flag in ImageJ.cfg file then ran ImageJ (either from console with no flags or by clicking icon), ImageJ loads and says 1024MB available under Help->About ImageJ, but only uses up to 505MB (50%)

Tried 3 and 4 with -mx* instead of -Xmx* and the result was the same, except IJ used 495MB before crashing.

What's the difference between -mx and -Xmx?