I actually added details to that bug report that was on the wiki. It had been listed as major bug, was downgraded, and then apparently removed. This thread here proves it is still a major bug.
My issues are pretty much as described above, have tried all the solutions listed (before even reading this thread!) and nothing.
I have enough ram that I can run several undead java processes before requiring a reboot, but it's still really annoying having to start a new minecraft process every time I log out of a server.
You guys could try ending the process tree using Process Explorer.
Process Explorer is developed by Sysinternals, and Sysinternals are a subsidiary of Microsoft; PE is published by MS, so you can be sure it's safe.
PE does not kill the processes either. They are really remakably persistant. I suspect there is some kind of GPU interaction going such that the processes cannot be released until 'something' happens.
I actually added details to that bug report that was on the wiki. It had been listed as major bug, was downgraded, and then apparently removed. This thread here proves it is still a major bug.
My issues are pretty much as described above, have tried all the solutions listed (before even reading this thread!) and nothing.
I have enough ram that I can run several undead java processes before requiring a reboot, but it's still really annoying having to start a new minecraft process every time I log out of a server.
PE does not kill the processes either. They are really remakably persistant. I suspect there is some kind of GPU interaction going such that the processes cannot be released until 'something' happens.
Mmm, good to know. How is it decided whether to remove a bug report?
I had also seen it in the Google cache, but not on the bug report page itself.
One of the reasons I suggested multimc, is it runs the console window in the background, thus allowing you to at least see any errors that might be occurring. It might also allow you to close the process, however if you can't end the program from the task manager, then you may be on to something about low level involvement preventing the shutdown process.
I too am experiencing this issue. Currently have 5 java processes running in the background eating up memory. It seems as if it could be a missing WindowClosing event handler for System.exit(0); though I have no idea how it could have been removed from the code where it previously existed. I never had this problem with minecraft before the last update, though I have experienced similar issues of java not closing with programs I wrote and forgot to add that bit of code in. I hope this gets resolved soon so I can stop having to log out after each time I play or minecraft crashes...
I too am experiencing this issue. Currently have 5 java processes running in the background eating up memory. It seems as if it could be a missing WindowClosing event handler for System.exit(0); though I have no idea how it could have been removed from the code where it previously existed. I never had this problem with minecraft before the last update, though I have experienced similar issues of java not closing with programs I wrote and forgot to add that bit of code in. I hope this gets resolved soon so I can stop having to log out after each time I play or minecraft crashes...
Logout does not work for me - it looks as if the processes are gone after logging back in, but they're not - show processes from all users reveals them again. Only a reboot works...
Logout does not work for me - it looks as if the processes are gone after logging back in, but they're not - show processes from all users reveals them again. Only a reboot works...
Aww snap, crackle, and pop. You are right. man, this problem is even more serious than i thought!
When you have 5-6 javaw.exe and your physical memory is like 80-99%....
You open a new minecraft
and you notice that the first minecraft you opened or the largest javaw.exe gets removed and replaced with the new javaw.exe you just opened.
Because Whenever I hit 100% physical memory, one of the javaw.exe will just close by itself.
I can confirm that this is affecting a computer with Intel Integrated Chipset. The error doesn't seem to be from a problem with any specific graphics card.
I can confirm that this is affecting a computer with Intel Integrated Chipset. The error doesn't seem to be from a problem with any specific graphics card.
Does this include people who have Intel Integrated Chipset, but forced minecraft to be ran by a specific graphics card?
When you have 5-6 javaw.exe and your physical memory is like 80-99%....
You open a new minecraft
and you notice that the first minecraft you opened or the largest javaw.exe gets removed and replaced with the new javaw.exe you just opened.
Because Whenever I hit 100% physical memory, one of the javaw.exe will just close by itself.
Anyone can repeat?
I'll certainly try it when I next have time to troubleshoot this!
Does this include people who have Intel Integrated Chipset, but forced minecraft to be ran by a specific graphics card?
Funny thing is, my laptops with Mobile Intel 4 Express chipset pretty much work OK. Only had the issue once, where MC crashed and the process was left hanging. Otherwise, it exits just fine on those.
Funny thing is, my laptops with Mobile Intel 4 Express chipset pretty much work OK. Only had the issue once, where MC crashed and the process was left hanging. Otherwise, it exits just fine on those.
This s actually my situation, and i'm getting this problem.
The
Java Virtual Machine exits when the only threads running are all
daemon threads.
Multi-threaded programs need to manage their threads carefully, otherwise it might not exit cleanly. A JVM update can always introduce new issues, but I'm more likely to blame a non-daemon thread that doesn't get terminated and cleaned up when the user tries to exit the program.
In the past few days I've been running into the same issue of java instances left running after quitting minecraft.
The thing is that I'm still running on 1.2.5, and yet I'm getting the same problem (despite numerous people saying it's not an issue with 1.2.5).
I have found however, that in my case it seems to be a problem with optifine's multi-threaded world loading feature.
If multi-threading is enabled when my client starts up, and then I quit the game, the java process is left running (BAD!).
If I change world loading to default/smooth, start my client and then quit, the java process closes normally (GOOD!).
I have recently updated my java to v7u7 (was on v7u3 or u4 I don't remember).
I'm wondering if the update has somehow changed how java multithreading works, causing it to stay running even after minecraft has been exited. (Note: I know nothing about programming in the slightest, so apologies in advance if this is complete drivel )
As I am able to reproduce the java process left running issue 100% of the time, I could upload a screen-recording showing the issue + how switching to optifine's smooth option seems to fix it.
Anyone else want to try using optifine smooth to see if it fixes the problem, and report it back here?
The thing is... Most of us in 1.3.1 get this problem without any mods installed at all.
FOUND A FIX! Play in browser. It will correctly shutdown the process. A bit inconvenient but better than rebooting your pc every time you play Minecraft.
Rollback Post to RevisionRollBack
If i helped you, Make sure to click the little "+" on the bottom right of my post.
FOUND A FIX! Play in browser. It will correctly shutdown the process. A bit inconvenient but better than rebooting your pc every time you play Minecraft.
I'm just going to go ahead and add my voice to this thread.
I'm running Windows 7 x64 and 64-bit Java 7 u7. ATI Graphics card (don't know which one, but probably not important - seems card-independent).
We also have a desktop that runs Windows Vista x64, also with an ATI Graphics Card. That one seems to have the problem more frequently, though my sister uses a lot of mods and it crashes frequently.
I also have the strange lock-up glitch, and it only occurs when I play multiplayer.
I don't believe it would be a problem with being unable to write save files - it happens when people play multiplayer, and the client doesn't have to write anything local in that case.
Rollback Post to RevisionRollBack
If you'd like to help me out, I think the best thing you could do is check out my YouTube channel, even more than voting up my reputation, though that'd be nice too.
My issues are pretty much as described above, have tried all the solutions listed (before even reading this thread!) and nothing.
I have enough ram that I can run several undead java processes before requiring a reboot, but it's still really annoying having to start a new minecraft process every time I log out of a server.
Windows 7 x64
Intel Core i7 Q740 @ 1.73 Ghz
16 GB RAM
GeForce 425M (1 GB)
PE does not kill the processes either. They are really remakably persistant. I suspect there is some kind of GPU interaction going such that the processes cannot be released until 'something' happens.
Mmm, good to know. How is it decided whether to remove a bug report?
I had also seen it in the Google cache, but not on the bug report page itself.
One of the reasons I suggested multimc, is it runs the console window in the background, thus allowing you to at least see any errors that might be occurring. It might also allow you to close the process, however if you can't end the program from the task manager, then you may be on to something about low level involvement preventing the shutdown process.
Logout does not work for me - it looks as if the processes are gone after logging back in, but they're not - show processes from all users reveals them again. Only a reboot works...
When you have 5-6 javaw.exe and your physical memory is like 80-99%....
You open a new minecraft
and you notice that the first minecraft you opened or the largest javaw.exe gets removed and replaced with the new javaw.exe you just opened.
Because Whenever I hit 100% physical memory, one of the javaw.exe will just close by itself.
Anyone can repeat?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumDoes this include people who have Intel Integrated Chipset, but forced minecraft to be ran by a specific graphics card?
I'll certainly try it when I next have time to troubleshoot this!
Funny thing is, my laptops with Mobile Intel 4 Express chipset pretty much work OK. Only had the issue once, where MC crashed and the process was left hanging. Otherwise, it exits just fine on those.
This s actually my situation, and i'm getting this problem.
You're having this problem on your laptop/s, yes?
FWIW, here's a full dump of my (MC mostly working) laptop spec:
Intel® Graphics Media Accelerator Driver for Mobile Report
Report Date: 9/10/2012
Report Time[hr:mm:ss]: 18:38:52
Driver Version: 8.15.10.2182
Operating System: Windows 7 Service Pack 1(6.1.7601)
Default Language: English (Canada)
DirectX* Version: 10.0
Physical Memory: 1999 MB
Minimum Graphics Memory: 32 MB
Maximum Graphics Memory: 807 MB
Graphics Memory in Use: 168 MB
Processor: Intel64 Family 6 Model 23 Stepping 10
Processor Speed: 2259 MHz
Vendor ID: 8086
Device ID: 2A42
Device Revision: 07
* Accelerator Information *
Accelerator in Use: Mobile Intel(R) 4 Series Express Chipset Family
Video BIOS: 1659.0
Current Graphics Mode: 1680 by 1050
* Devices Connected to the Graphics Accelerator *
Active Digital Displays: 1
* Digital Display *
Monitor Name: Dell E228WFP
Display Type: Digital
Gamma Value: 2.2
DDC2 Protocol: Supported
Maximum Image Size:
Horizontal: 18.50 inches
Vertical: 11.81 inches
Multi-threaded programs need to manage their threads carefully, otherwise it might not exit cleanly. A JVM update can always introduce new issues, but I'm more likely to blame a non-daemon thread that doesn't get terminated and cleaned up when the user tries to exit the program.
The thing is... Most of us in 1.3.1 get this problem without any mods installed at all.
Testing this. Sounds wierd, but it's worth a try.
nope.
My browser uses java.exe 32 bit while my minecraft uses javaw.exe 64 bit.
Doesn't work for me.
It worked the first time and stopped working again. Back to square one again. Sorry for the false alarm.
Nor me - the only difference is it leaves a java.exe *32 bit process rather than javaw.exe as a zombie task.
I'm running Windows 7 x64 and 64-bit Java 7 u7. ATI Graphics card (don't know which one, but probably not important - seems card-independent).
We also have a desktop that runs Windows Vista x64, also with an ATI Graphics Card. That one seems to have the problem more frequently, though my sister uses a lot of mods and it crashes frequently.
I also have the strange lock-up glitch, and it only occurs when I play multiplayer.
I don't believe it would be a problem with being unable to write save files - it happens when people play multiplayer, and the client doesn't have to write anything local in that case.