mojira.dev

When streaming MC using the OpenGL Game Source, a memory leak occurs causing the game to use as much RAM as it wants. This started in 1.7, and not any previous versions of the game.

For example, Minecraft shows it is using 450MB of RAM in-game, but task manager is reporting java.exe is using 11.5GB of RAM. I tracked it over an hour and the process went from matching the in-game RAM usage to maxing out my system.

Comments 9

Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report ([minecraft|http://hopper.minecraft.net/help/finding-minecraft-data-folder]/crash-reports/crash-<DATE>-client.txt) here.

and

Please attach the complete output of the "Development console" tab of the launcher.

  • Click the text, press CTRL-A to select all, then CTRL-C to copy, and CTRL-V to paste in a comment on this ticket.

If the launcher closes after game start, please edit your profile and select "Launcher visibility" then, "Keep the launcher open".

Do I need to force crash just playing or while streaming via OpenGL source? Or would you like both? Note: The memory leak only occurs when streaming via OpenGL Source.

Uhm, sorry, what is OpenGL Source ?

Sorry I didn't explain it very well. To stream Minecraft you used to either choose a game source DX11, or game source OpenGL. Since 1.7, only the OpenGL game source is available, and something about streaming via that in 1.7 (not previous versions), causes java.exe to have a memory leak. This is fairly problematic for the large amount of people streaming MC out there.

Invalid since not a Minecraft issue.

Is it not considered a minecraft issue due to it being the update to 1.7 causing it? And the leak being in the java.exe process minecraft runs off?

I would guess because it's a 3rd party program, therefor it's not supported.

This bug tracker is only for Minecraft itself, not for any issue with it's interaction with 3rd party stuff.

Ok. I just assumed it was something to do with minecraft due it being a change in minecraft that causes the issues. I guess it's just the way the streaming program(s) handle the new code.

Guy Mawson

(Unassigned)

Unconfirmed

leak, memory, openGL

Minecraft 1.7.1, Minecraft 1.7.2

Retrieved