Well there are couple of things. Program will start with -Xms value and if the value is lesser it will eventually force GC to occur more frequently Once the program reaches -Xms heap, jvm request OS for additional memory and eventually grabs -Xmx that requires additional time leading to performance issue, you might as well … Read more
The flag Xmx specifies the maximum memory allocation pool for a Java Virtual Machine (JVM), while Xms specifies the initial memory allocation pool. This means that your JVM will be started with Xms amount of memory and will be able to use a maximum of Xmx amount of memory. For example, starting a JVM like … Read more
Most of the times this is a bug in the VM. But it can be caused by any native code (e.g. JNI calls). The hs_err_pidXXX.log file should contain some information about where the problem happened. You can also check the “Heap” section inside the file. Many of the VM bugs are caused by the garbage … Read more
Could it be that you’re using a 32-bit jvm on that machine?
Run the JVM with -XX:MaxHeapSize=512m (or any big number as you need) (or -Xmx512m for short)
Ultimately you always have a finite max of heap to use no matter what platform you are running on. In Windows 32 bit this is around 2GB (not specifically heap but total amount of memory per process). It just happens that Java chooses to make the default smaller (presumably so that the programmer can’t create … Read more
Ultimately you always have a finite max of heap to use no matter what platform you are running on. In Windows 32 bit this is around 2GB (not specifically heap but total amount of memory per process). It just happens that Java chooses to make the default smaller (presumably so that the programmer can’t create … Read more
Run the JVM with -XX:MaxHeapSize=512m (or any big number as you need) (or -Xmx512m for short)