I have a feeling this has to do with the ninja fix to "trick" the Intel Drivers for performance.
Basically, opening Minecraft will inconsistently (sometimes it happens, sometimes it doesn't) open up 3 javaw.exe processes viewable from the Task Manager. Normally, it opens two; the javaw.exe for the launcher and the javaw.exe for the game. This third, fake process eats CPU usage and memory like...well to be honest the only analogies I can come up with are either offensive or so out of mainstream culture so...basically at it's worst, the fake javaw was using 96% of the CPU and over a million KB of memory. It has since died down this behavior and capped itself around 800,000 KB and 25% of the CPU, but this is still a lot. Ending the fake process does nothing visible to affect the game.
Attached are screenshots of my Task Manager.
Edit for August 1st, 2013: I have so far been unable to reproduce the fake javaw process. However, I have identified that the one eating the CPU isn't the fake process, but the launcher.
Related issues
Attachments
Comments
migrated
kumasasa
Cannot confirm.
Please switch on the column "Command line" in the task manager (Appearance -> Select Columns... -> Command line) and redo the screenshots.
migrated
I seem to be unable to reproduce as well now; as I only get the TrickingIntelDrivers (the one that controls Minecraft itself) and the launcher. If it happens again, I'll screenshot the Taskmanager and update the ticket.
kumasasa
Question: You didn't have Eclipse running while that issue ?
migrated
Updated. Enourmous memory is not, as I first assumed, eaten by the fake process I saw, but by the launcher. See attached "million.gif" file. Minecraft.exe is the launcher, it uses (in the picture) 1,140,712 KB of memory and 91% of the CPU (though this fluctuates).
I have edited the ticket accordingly.
Kumasasa: Sorry, not all that technical savy, all that is running (rather, what I've opened) is:
The Minecraft game folder in Windows Explorer
Chrome
And Minecraft itself (the launcher, as specified by Dinnerbone, remains running to catch crashes)
kumasasa
The question for Eclipse was to identify the third "fake" Java process (Eclipse runs also under Java...)
Regarding the high mem usage and cpu load of the launcher: Did you have a world which spams the logfile ? See MCL-1291
migrated
It might have been, for both of those.
Definitely for the spamming the logfile, so much so that I cannot load a majority of the output. In that case you can close this ticket and mark MCL-1291 as affecting launcher version 1.2
kumasasa
Resolved.