bat script will use 32-bit JDK by default (from the. exe (also useful if 64-bit executable is not provided for your product).
Start in 64-bit mode, for example IntelliJ IDEA provides idea64.exe launcher that will use 64-bit JDK found in the registry (you have to install it separately). Refer to the Configuring JVM options and platform properties for details. Reduce -Xmx and -XX:PermSize values in IDE_HOME\bin\.exe.vmoptions file, try to do it step by step reducing by 100m every time until it starts. 
IntelliJ IDEA 13.1.x+ versions have a new launcher version that doesn't cause memory fragmentation because of the splash screen. exe launcher can itself cause additional fragmentation, we are using a third-party tool for this launcher and do not have full control over it, but in the future updates we'll migrate to our own launcher that should reduce the fragmentation. The more third-party libraries you see there, the higher is the chance that the address space will get fragmented and you will get this error even with low heap values. Some common dynamic libraries that you can observe: TortoiseOverlays.dll, mdnsNSP.dll, Dropbo圎xt.dll. Use the DLLs view ( Ctrl + D ) in the Process Explorer to find out what apps injected their hooks into the IDE process. Some applications inject DLLs into the address space of other processes leading to fragmentation. Your system may have a lot of different application installed and running.
Address space fragmentation can heavily limit the maximum heap size that can be used. There might be no such chunk available in the address space to fit in the heap. Even if total memory doesn't exceed the OS limit, JVM requires all the heap memory to be continuous. All these factors make it easy to get close or exceed the 2GB value. 
Heap size is not the total memory limit, the value of -XX:PermSize is also added to this number, plus stack size for every thread, plus memory mapped files, plus internal JVM memory for the JIT compiler and other needs. IDE runs in 32-bit mode by default which limits the total amount of process memory that can be addressed to 2GB on most Windows versions.Įven if the maximum heap size ( -Xmx) is set to just 512m, you can still observe this problem for the following reasons: Recent IDE versions with the new launcher fail with this error instead: Failed to create JVM: error code -4. 
This Windows specific problem can occur if Java Virtual Machine can't allocate the specified amount of memory in a single continuous chunk when you start the IDE.
0 kommentar(er)
