[MC-35454] Excessive memory uses

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=16

the 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.

Comments 7

kumasasa 2013-10-15T22:03:05Z

Leave out -Xmx512M -Xms256M -XX:+TieredCompilation -dsa -da -XX:+AggressiveOpts -XX:+UseFastAccessorMethods -XX:MaxGCPauseMillis=2 -XX:GCPauseIntervalMillis=16 and let do the JVM the GC.

Thomas Jones 2013-10-15T22:06:53Z

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.

Thomas Jones 2013-10-15T22:08:53Z

Also I tested 13w39b and it works just fine.

Neospector 2013-10-15T23:32:23Z

Question, and I know nothing about Linux here, what's the console output on the game looking like?
I found that MCL-1291 still occurs on at least one map on a certain version.

Thomas Jones 2013-10-15T23:55:59Z

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

Ezekiel 2013-11-27T19:46:08Z

Is this still a concern in the latest Minecraft version 13w48b? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Talven81 2014-01-15T18:52:08Z

This ticket is invalid without the requested information, no response has been received within a reasonable time and we are assuming the issue has been resolved. If you are still experiencing this issue, we can reopen it at your request.