Thomas Jones
- Spudd86
- spudd86
- Europe/Stockholm
- Yes
- No
MC-35454On start up the java process allocates a massive amount of memory (during the Mojang screen), it's not the Java heap because my JVM arguments are
-Xmx512M -Xms256M -XX:+TieredCompilation -dsa -da -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -XX:MaxGCPauseMillis=2 -XX:GCPauseIntervalMillis=16the virtual memory of the process rapidly went up to 2GB before the menu even shows, and since I only have 2GB of memory everything went very slow and Minecraft continued to allocate more and more memory, it was over 4GB before the menu showed. It normal only ends up with about 300MB RSS at the main menu
On start up the java process allocates a massive amount of memory (during the Mojang screen), it's not the Java heap because my JVM arguments are
-Xmx512M -Xms256M -XX:+TieredCompilation -dsa -da -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -XX:MaxGCPauseMillis=2 -XX:GCPauseIntervalMillis=16the virtual memory of the process rapidly went up to 2GB before the menu even shows, and since I only have 2GB of memory everything went very slow and Minecraft continued to allocate more and more memory, it was over 4GB before the menu showed. It normal only ends up with about 300MB RSS at the main menu, The snapshot the RSS rapidly shoots up to about 1.4GB and stays there while the system thrashes.
I am letting the JVM do the GC, I limited the JVM heap size...
I tried again with JVM args off, same thing only worse.
Also I tested 13w39b and it works just fine.
There's really nothing in the console, just the usual startup messages, and something about the audio system failing to set it's thread to realtime priority, which isn't really important, and isn't surprising or unusual