Posted by Wade Walker on Jun 19, 2011; 2:45am
URL: https://forum.jogamp.org/Crash-when-creating-more-than-15-jogl-awt-windows-tp3054540p3081667.html

If you're using a 32-bit JVM on Windows, there is an unexpectedly low limit on heap size. Programs can usually only get maybe 1.5 GB of heap at maximum, depending on how much other memory the program uses (the whole JVM process can only have 2GB at theoretical max on 32-bit Windows). So setting -Xmx to 1.5G might allow the Java heap to crowd out other memory use by the process, which could lead to errors in native/JNI code. Lowering -Xmx might be forcing more frequent garbage collection and leaving more room for non-heap memory use.