MC-2258Client uses 100% CPU
The Minecraft client always occupies 100% of one core. In turn, this makes the desktop environment itself quite unresponsive. The game is somewhat responsive, but it slows down tremendously at times (as the system struggles to catch up).
Environment
Core i5 2.8 GHz
4 GB RAM
NVIDIA GTX 275
Tested in both Ubuntu 12.04 (64-bit) and Mint 13 (64-bit).
Tested in both Oracle Java 7 and OpenJDK 7.
Used proprietary NVIDIA driver (binary blob).
Created Issue:
Client uses 100% CPU in Linux
The Minecraft client always occupies 100% of one core. In turn, this makes the desktop environment itself quite unresponsive. The game is somewhat responsive, but it slows down tremendously at times (as the system struggles to catch up).
Environment
Core i5 2.8 GHz
4 GB RAMTested in both Ubuntu 12.04 and Mint 13.
Tested in both Oracle Java 7 and OpenJDK 7.
Core i5 2.8 GHz
4 GB RAM
NVIDIA GTX 275Tested in both Ubuntu 12.04 and Mint 13.
Tested in both Oracle Java 7 and OpenJDK 7.
Core i5 2.8 GHz
4 GB RAM
NVIDIA GTX 275Tested in both Ubuntu 12.04 and Mint 13.
Tested in both Oracle Java 7 and OpenJDK 7.
Used proprietary NVIDIA driver (binary blob).
Core i5 2.8 GHz
4 GB RAM
NVIDIA GTX 275Tested in both Ubuntu 12.04 (64-bit) and Mint 13 (64-bit).
Tested in both Oracle Java 7 and OpenJDK 7.
Used proprietary NVIDIA driver (binary blob).
Client uses 100%CPU in Linux
Client uses 100% CPU
![[Mod] Jiingy](../../../data/avatars/users/91802.png){kind=small}
Minecraft is not intended to use 100% of your GPU and CPU, as that would disallow any other functions of your computer from properly operating, and would additionally lead to crashes and/or freezing as denoted by other issues on the bug tracker such as; MC-2258 MC-208265 and MC-232707 (resolved into MC-219639)
As with most of these kinds of issues, please refer to community support.
I am a game developer myself.
<StabInTheDark> This behavior presents itself when there is a loop in the code with absolutely no sleep calls. Oftentimes, when developers build their first game loop, the game eats 100% needlessly because the application never relinquishes control of the CPU. So, there is likely a loop or two in the code that would really benefit from a 1 millisecond sleep (or even 0 millisecond sleep). </StabInTheDark>
This is the first time I've heard of this. How much memory are you allocating to the game? Have you updated your LWJGL?
I've allocated 2 GB and 4GB to the client with no change. One core hits 100% and stays there. Even if I stand still and do nothing, it stays at 100%.
And yes, I've updated my LWJGL. Are you referring to one beside the one that the Minecraft client manages/updates?
I also have this issue, it is the same ever since Alpha 1.2_01 (that's when I started playing).
I have the same problem on 64 bit Fedora on my HP EliteBook 8540p . I actually had this problem on the same machine when I ran Ubuntu years ago.
The performance of the game is flawless even with higher graphics settings but even with low settings the java process will hog 120% CPU. Eventually the computer will turn itself off to prevent the CPU from overheating.
There are sleeps in the main loop.
When is it using 100%? What are you doing at that moment? it can be totally justified if you have a sub-par machine, which in this case is not really likely.
It is using 100% all the time. I can stand still, and it will stay at 100%. I can walk around, and it will stay at 100%. It will periodically shift which core is maxed, but one of them is always maxed. And yeah, as noted in my specs above, my computer is no slouch. If I run the game in Windows, this problem does not exist.
I updated the environment to clarify: I am indeed running 64-bit.
And yeah, I figured you had sleeps in the code. (If you didn't, the Windows and Mac versions would be crying out loud right now.) This makes me wonder if there is something wrong with the Linux JVM and/or its handling of timers/sleeps.
Is it just me, or does it seem that every linux related problem I've seen be on computers that use NVIDIA graphics?
Feel free to attach a profiler to the JVM and report back with some hotspots
Good news. The update 1.4.5 seems to have fixed it. Granted, I don't know whether it was Minecraft's update or one of my system updates to Ubuntu/NVIDIA that fixed it. It patches so often. I will keep an eye on it. I think the real test will be in making a new world and playing some heavy duty multiplayer.
I did manage to attach VisualVM (profiler) to it. Sadly, it made the game unplayable. XD But if you ever want a snapshot from that, I can post it here.
Still having this issue in 1.4.5. I'm running Ubuntu 12.10 with the latest NVIDIA drivers. The issue happens both with OpenJDK 7 and Oracle Java 7. I'll try upgrading LWJGL.
Turns out I had already upgraded LWJGL. At first when I run the game, everything works fine. After a while, the game becomes very unresponsive. The debug screen indicates that the render is taking up the most time (over 90%). The game is very slow even after I close the world and go to the title screen. The Xorg process takes up 100% CPU and my machine only becomes responsive again when I close Minecraft.
In my last world, this didn't happen as frequently. I just started a hardcore world in default world generation mode, and the problem is happening only within a minute of starting the game. My seed is 12345.
EDIT: the biome I spawned in is ForestHills, which seems to be causing the most trouble.
Try without fancy graphics.
If it's fine, leaves are broken
I just noticed in my terminal window there's lots of error messages.
Nov 24, 2012 10:20:13 AM bdo c INFO: Starting integrated minecraft server version 1.4.5 Nov 24, 2012 10:20:13 AM bdo c INFO: Generating keypair Nov 24, 2012 10:20:13 AM net.minecraft.server.MinecraftServer e INFO: Preparing start region for level 0 Nov 24, 2012 10:20:14 AM gm a INFO: pantalones[/127.0.0.1:0] logged in with entity id 366 at (299.30000001192093, 67.0, 254.34965280381195) Nov 24, 2012 10:20:47 AM bdo q INFO: Saving and pausing game... Nov 24, 2012 10:20:47 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Overworld Nov 24, 2012 10:20:47 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Nether Nov 24, 2012 10:20:47 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/The End Nov 24, 2012 10:21:51 AM bdo q INFO: Saving and pausing game... Nov 24, 2012 10:21:51 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Overworld Nov 24, 2012 10:21:51 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Nether Nov 24, 2012 10:21:51 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/The End Nov 24, 2012 10:22:42 AM bdo q INFO: Saving and pausing game... Nov 24, 2012 10:22:42 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Overworld Nov 24, 2012 10:22:42 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Nether Nov 24, 2012 10:22:42 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/The End Something's taking too long! 'root.render.display' took aprox 1013.624268 ms Something's taking too long! 'root.render' took aprox 1013.825029 ms Something's taking too long! 'root' took aprox 1024.570369 ms Something's taking too long! 'root.render.display' took aprox 2470.706423 ms Something's taking too long! 'root.render' took aprox 2470.788585 ms Something's taking too long! 'root' took aprox 2487.646667 ms Something's taking too long! 'root.render.display' took aprox 2067.259886 ms Something's taking too long! 'root.render' took aprox 2067.343412 ms Something's taking too long! 'root' took aprox 2107.529917 ms Something's taking too long! 'root.render.display' took aprox 2026.06583 ms Something's taking too long! 'root.render' took aprox 2026.263376 ms Something's taking too long! 'root' took aprox 2054.399572 ms Something's taking too long! 'root.render.display' took aprox 2520.830052 ms Something's taking too long! 'root.render' took aprox 2520.901128 ms Something's taking too long! 'root' took aprox 2538.474859 ms Something's taking too long! 'root.render.display' took aprox 1126.527453 ms Something's taking too long! 'root.render' took aprox 1126.610478 ms Something's taking too long! 'root' took aprox 1146.12424 ms Something's taking too long! 'root.render.display' took aprox 1071.022463 ms Something's taking too long! 'root.render' took aprox 1071.103307 ms Something's taking too long! 'root' took aprox 1098.8229 ms Something's taking too long! 'root.render.display' took aprox 892.242964 ms Something's taking too long! 'root.render' took aprox 892.325314 ms Something's taking too long! 'root' took aprox 915.452684 ms Something's taking too long! 'root.render.display' took aprox 2807.951153 ms Something's taking too long! 'root.render' took aprox 2808.135777 ms Something's taking too long! 'root' took aprox 2826.192288 ms Something's taking too long! 'root.render.display' took aprox 981.45817 ms Something's taking too long! 'root.render' took aprox 981.599116 ms Something's taking too long! 'root' took aprox 997.303602 ms Something's taking too long! 'root.tick.keyboard' took aprox 1140.63165 ms Something's taking too long! 'root.tick' took aprox 1163.049538 ms Something's taking too long! 'root' took aprox 1222.495568 ms Nov 24, 2012 10:24:55 AM bdo q INFO: Saving and pausing game... Nov 24, 2012 10:24:55 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Overworld Nov 24, 2012 10:24:55 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Nether Nov 24, 2012 10:24:55 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/The End Something's taking too long! 'root.render.display' took aprox 2255.810253 ms Something's taking too long! 'root.render' took aprox 2255.946345 ms Something's taking too long! 'root' took aprox 2268.139559 ms Something's taking too long! 'root.render.display' took aprox 818.155493 ms Something's taking too long! 'root.render' took aprox 818.225852 ms Something's taking too long! 'root' took aprox 839.28975 ms Something's taking too long! 'root.render.display' took aprox 1029.763252 ms Something's taking too long! 'root.render' took aprox 1029.855715 ms Something's taking too long! 'root' took aprox 1049.46245 ms Something's taking too long! 'root.render.display' took aprox 1023.340792 ms Something's taking too long! 'root.render' took aprox 1023.427342 ms Something's taking too long! 'root' took aprox 1032.406619 ms Something's taking too long! 'root.render.display' took aprox 987.620904 ms Something's taking too long! 'root.render' took aprox 987.713412 ms Something's taking too long! 'root' took aprox 1000.235272 ms Something's taking too long! 'root.render.display' took aprox 1028.45079 ms Something's taking too long! 'root.render' took aprox 1028.553837 ms Something's taking too long! 'root' took aprox 1041.218642 ms Something's taking too long! 'root.render.display' took aprox 1023.608014 ms Something's taking too long! 'root.render' took aprox 1023.702448 ms Something's taking too long! 'root' took aprox 1043.402356 ms Something's taking too long! 'root.render.display' took aprox 3768.276201 ms Something's taking too long! 'root.render' took aprox 3768.492364 ms Something's taking too long! 'root' took aprox 3787.470706 ms Something's taking too long! 'root.render.display' took aprox 2431.957428 ms Something's taking too long! 'root.render' took aprox 2432.105665 ms Something's taking too long! 'root' took aprox 2444.945722 ms Something's taking too long! 'root.render.display' took aprox 1039.144553 ms Something's taking too long! 'root.render' took aprox 1039.23689 ms Something's taking too long! 'root' took aprox 1056.113403 ms Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer k INFO: Stopping server Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer k INFO: Saving players Something's taking too long! 'root.tick.textures' took aprox 352.508112 ms Something's taking too long! 'root.tick' took aprox 352.678534 ms Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer k INFO: Saving worlds Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Overworld Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/Nether Nov 24, 2012 10:25:13 AM net.minecraft.server.MinecraftServer a INFO: Saving chunks for level 'Foo'/The End Something's taking too long! 'root.render.display' took aprox 3177.691511 ms Something's taking too long! 'root.render' took aprox 3177.802317 ms Something's taking too long! 'root' took aprox 3540.422126 ms Stopping! SoundSystem shutting down... Author: Paul Lamb, www.paulscode.comI just installed Mint 14 64-bit. (I abhor Unity, but I love Ubuntu repos.)
I am running Mint 14 MATE with no compiz. So far, no 100% CPU usage issues. It spikes when (presumably) it has to load new areas, but general gameplay is fine. I will begin enabling certain desktop effects/compositors and see if that affects the CPU.
Changing from fancy to fast graphics after Minecraft goes to 100% CPU has no effect.
edit:
I had totally forgotten about this. I deleted my post because I found out that it was not a similar issue for me, so my post was irrelevant to this ticket.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
The problem seems gone for me. I'm still running the same hardware with Mint 14 MATE and OpenJDK (64-bit). Again, I have no idea if it was a kernel update, a Java update, or a Minecraft update (or combination of those), but the CPU only spikes briefly when loading world chunks. General gameplay falls below 100%. So, for what it's worth, I have not observed this problem in 1.5.1.
I hope it is fixed for everyone. It is an issue worth monitoring. When the problem was happening, my system became unresponsive. It really was using 100% at the expense of everything else. I couldn't even drag a Nautilus/Caja window across my desktop; it was so bad.
No more updates, assuming no longer an issue.