Hi, so today i noticed that bukkit has started taking like 70% to 100% of my CPU power and its strange becuase it was running just fine yesterday and earlier today and i havent updated bukkit or any plugins or added any new plugins in quite some time so that cant be it. Any ideas on why it started doing this and/or how i can fix it? Tell me if you need more information and ill update the post. OS: Windows 7 Ultimate 64 Bit Java's: Java(TM) SE Runtime Environment (build 1.6.0_24-b07) Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode) Wrappers: None, i only use bukkit with plugins. Bukkit: Build #803 (2011-may-22 21:22:01) Start.bat: Code: @ECHO OFF SET BINDIR=%~dp0 "C:\Program Files (x86)\Java\jre6\bin\java.exe" -Xincgc -Xmx1G -jar "%BINDIR%\craftbukkit-0.0.1-SNAPSHOT.jar" PAUSE Plugins: Code: AdminRage Essentials EssentialsChat EssentialsGeoIP EssentialsSpawn Lockette MagicCarpet Permissions WorldEdit WorldGuard Errors: Not getting any Tried: Restarting Computer, New World, No Plugins CPU: DualCore Intel Core 2 Duo E7500, 2933 MHz (11 x 267) Ill post if the things in that thread helps.
I have this issue with my old AMD Sempron 3400+, AM2 socket dedicated server. I really need to upgrade.
I had 766 before, and when the cpu went up i updated to 803. So note that the cpu was 100% with 766 to.
Create a new map, see if it continues. Anyway, a 100% CPU usage isnt something odd. I do run my server (50 plugins, 30 people) using usually 97% core load. But, before my current map, I had this same problem with a very old map, it used 100% core load with 3 or 4 guys, could only solve it reseting the map
I tried new world and it didnt work and then i tried it again and it worked. How weird, but now when i updated to 1.6.4 and join the server it wont load the world or it loads it really really slowly.
he also said on http://www.minecraftwiki.net/wiki/Version_history#Beta "CPU issue fix is still failing, same loop as 1.6.3"
Fuck, I missed that part, Its sooo fucking annoying, I have my server set to reboot every 3 hours, That solves it
Hopefully a fix for that will come out pretty quickly sometime tomorrow as this is a rather major bug or glitch.