When I play the game I have serious performance issues and frame rate spikes and general slowness. When I open task manager I see that javaw.exe is running over 1.2 GB in memory. When I save and quit to the main screen this memory usage remains at over a Gigabyte for several minutes. This is a clear symptom of a memory leak as the program is tying up memory that is unnecessary for what the program is doing. I have 5 screenshots with the minecraft window over the task manager showing the increasing amount of RAM that is being used by the Minecraft javaw.exe application. During this test I did not move far from where I started when I loaded the game. Please fix this game breaking bug.
Attachments
Comments 3
So instead of fixing the performance issues you just pretend that they don't exist?
Look at the last picture. This is after I have been out of the actual game for well over 5 minutes please explain to me how there is a need for the program to be utilising 1.246 GB of memory when the program is idling on the main screen. Dont make me post another bug report with screenshots with previous stable releases showing how they don't behave like this because they don't have a line of code dumping garbage into RAM every time it is called(a memory leak).
I have to concur with Matthias here. I continually get a massive amount of memory being hogged by the background launcher. Upwards of 270000K. For a program running idle, this is really unwarranted. General consensus of those I am in contact with is the same. In fact, we all seem to ctrl-alt-delete the windows process, which defeats the purpose of it running. I recently had a twitter conversation with Dinnerbone about it. He said the launcher is meant to run in the background, but it seemed he was surprised at the amount of RAM it was taking up.
I feel this issue should be reopened.
Here's the conversation with Dinnerbone I had over the excessive RAM.
https://twitter.com/theqmagnet/status/500614997043847168
There is no memory leak, that's the way Java / the JVM works.
The amount of heap you've allocated for the JVM is 1 GB , see in your screenshots the top left corner "... of 910 MB", the rest is the JVM itself, the stack etc.
Read on here: http://www.oracle.com/webfolder/technetwork/tutorials/obe/java/gc01/index.html