Guy Mawson

This is no longer an issue as far as I know.

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.

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?

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.

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.

As I said it does not happen every time I play and have not had it in either 1.6.1 or 1.6.2 for a couple of days.

So I've gotten that fed up of this issues I have completely re-installed Windows. Just got java and minecraft back, and it seems to be working ok. Played for about 20 minutes so not conclusive yet, will comment once I've logged more hours.

Could it be a possibility that a part of the Minecraft code is actually forcing a part of the graphics driver to degrade over time this resulting in this issue? I've found that if I do a clean install of the drivers, the game will run flawlessly for roughly 6 hours (tested 7 times so far) and then will crash out and post a java.log to desktop. Is this a possibility, and if so would you then consider looking into it?

I doubt that unless this affects thousands or tens of thousands of people instead of a couple of hundred, it will ever be fixed and we'll all just be told it's not a minecraft issue.

I have tried running the game with Threaded Optimization disabled in my GPU Settings, I also have OpenGL disabled in the Minecraft Video Settings. I've even tried manually updating LWJGL.

So basically I have to wait and hope that nVidia will fix this just on an off chance even though they haven't in well over a year of issues?

(Just a note, I'm not the only one having this issue. I found at least 100 separate cases on various forums.)

I cannot play the game long enough to force a crash anymore, however I did force this crash last time I posted this issue to the tracker.

This has been happening for a very long time, yes. From around release I have had issues with the game crashing and posting the log I attached to my desktop, however it lately just crashes my PC and I am lucky if I can be in game for more than 5 seconds. I have a crash log from the last time I posted this issue.

The issue is worse in the new launcher, causing the game to bug out graphically too with a sort of "X-ray" effect everywhere. If you put your head in glowstone, you get the effect, however this was just everywhere walking around.

Would you mind explaining how you came to the conclusion this is a technical issue please? Just because the problem reports the issue being the library, does not necessarily mean it's a "technical issue".

Aaaand another crash (1.5.1). HUD disappeared and it froze my entire pc. Had to force shutdown (hold button in).

PLEASE help me.

1.5.1 All entities disappeared then the game just closed itself. Posted this file to desktop.

Just had another crash (1.5.1), attached the file.
http://puu.sh/2F35s.log Mirror

Windows crash logs are not originals but all the data is there.

It's not a bug, you've always been able to do this. That's how people make underwater air pockets 🙂

Ok I crashed the snapshot using F3+C, java went into not responding and windows popped up saying it had written 3 files which may help to find a solution. I cannot get the snapdhot to write a crash log into .minecraft no matter how many times I try this, it just goes into "Not Responding". Here are the 3 files windows created on the crash, and the launchers console:
http://puu.sh/2DwHM.xml
http://puu.sh/2DwIp.txt
http://puu.sh/2DwIQ.mdmp
http://puu.sh/2DwZj.txt

I also crashed Minecraft 1.5.1 and it actually wrote a crash log for once:
http://puu.sh/2DwVM.txt

Output-Client since I upgraded to 1.5.0 basically. http://puu.sh/2Dimk.log