After updating to version 1.3.1. Something really strange is going on that I believe is a bug in the source code of Minecraft itself relating to a hardware incompability issue.
Everytime I load minecraft v1.3.1, if I LOG INTO A WORLD, (SERVER OR SINGLEPLAYER), once I quit back to the main menu and exit the game via quit or red "X" icon. The javaw.exe stays running inside RAM memory. I cannot taskkill it in CMD neither can I end the process in Task Manager (nothing simply happens). Even though it says javaw.exe or java.exe (when opening the client with CMD) has successfully been termined it stills shows in the task manager, and the RAM is still being used or at least treated as it being used on my CPU|RAM usuage gadget gauge. If I load up minecraft client again, a new javaw.exe gets formed inside memory and as you see it really adds up and hogs my RAM memory a lot.
This ONLY HAPPENS AFTER LOGGING INTO A WORLD. If I start up the client and exit the game before logging into a world the javaw.exe will exit fine.
I have tested this with version 1.2.5, and it DOES NOT do this. So I believe it is a v.1.3.1 issue.
I have reinstalled java, resetted path, everything you can possible do to troubleshoot a java issue. Because I program in Java myself and am pretty familiar with Java.
I have JRE 7 Update 5. I have uninstalled my Java SDK just to make sure it wasn't affecting it. I have also tried running it on the newest SDK also. Currently at the moment only JRE 7 Update 5 is installed on my system.
Overall troubleshooting I have tried:
Exit game via "X" icon. (still runs in memory)
Exit game via quit. (still runs in memory)
Resetted Java Path in environmental variables.
Resetted Jar File association path.
Deleted minecraft folder from appdata folder, performed clean installs of minecraft.
Ran Minecraft from doubleclicking and from CMD.
Ending Process and Process Tree does not work. (Nothing happens, no prompt message or anything).
Version 1.2.5 works perfectly.
Any further questions please ask.
Here are my system specs:
Win 7, 64-bit, Home Premium
Intel Core i7-2670QM
Intel HD Graphics Family 3000
I have this exact same problem as described already found out this myself. whoever is developing minecraft should fix this... http://www.java.net/node/676794
when exiting in anyway, it keeps the memory. this needs to be fixed ASAP!
btw... add to his 64-bit Win7 specs my:
Intel Celeron (fossil i kno)
32-bit Vista Home Basic.
I'm on the other side of the table - so i think we've proved it's all across the board.
(i'm good at memory management, so my comp being old is not the prob)
(1.2.5 worked fine for me too)
(i ran every clean reinstall of java, everything. EVERYTHING. all that he did. it's MC's fault.
Yes I agree, this is a MAJOR issue, especially when the app eventually crashes and you need to reboot to recover enough memory to start again. I'm in a perpetual mode of play 10 min reboot play 10 min.
HELLO...Minecraft developers...are you listening...?