You may be able to use jsadebugd (JDK) to attach a debug server to the process (available on Windows with the Debugging Tools for Windows). It is marked as experimental, so you may want to try it out on a test machine first. Usage: jsadebugd <pid> jdb -connect sun.jvm.hotspot.jdi.SADebugServerAttachingConnector:debugServerName=localhost The connector name withe arg can … Read more
Current version: Help | Change Memory Settings: Since IntelliJ IDEA 15.0.4 you can also use: Help | Edit Custom VM Options…: This will automatically create a copy of the .vmoptions file in the config folder and open a dialog to edit it. Older versions: IntelliJ IDEA 12 is a signed application, therefore changing options in … Read more
Update This answer is relevant for Java 5-7, Java 8 has this fixed: https://blogs.oracle.com/poonam/about-g1-garbage-collector,-permanent-generation-and-metaspace Kudos go to mt.uulu For Java 5-7: The standard Oracle/Sun VM look on the world is: Classes are forever. So once loaded, they stay in memory even if no one cares anymore. This usually is no problem since you don’t have … Read more
Open the Run Configuration for your application (Run/Run Configurations…, then look for the applications entry in ‘Java application’). The arguments tab has a text box Vm arguments, enter -Xss1m (or a bigger parameter for the maximum stack size). The default value is 512 kByte (SUN JDK 1.5 – don’t know if it varies between vendors … Read more
You have pretty much nailed it except that these options are picked up even if you start JVM in-process via a library call. The fact that _JAVA_OPTIONS is not documented suggests that it is not recommended to use this variable, and I’ve actually seen people abuse it by setting it in their ~/.bashrc. However, if … Read more
At startup pass this -Dname=value and then in your code you should use value=System.getProperty(“name”); to get that value