Exploring a large cave system that my strip mine encountered around y:40 began to induce severe framerate drops and freezes. A unique 'slow-motion' effect takes place as the framerates and memory return to normal, only to be affected again shortly after if I were still in the area. Framerates would drop from 120 to 40 to 0 (readable in between screen freezes), CPU utilization on one (of eight) cores would spike from ~20% to ~90%, in-game memory would spike from 200 mb to 900 mb when this occurs. The issue occurs in the same general area, with no redstone or running water (cave cleared of water sources) and nothing but generated terrain. It can occur while moving or standing still. The internal server appears to continue to run, as mobs have attacked me in this crippled condition. Leaving the area will resolve the issue, and no issues will be present when visiting the same X, Z coordinate but on the surface.
Immediately preceding the issue is a series of quick freezes that do not appear to show any debug output. They are followed by the aforementioned issue. Viewing the debug console during the 'event', the 'Clientside Chunk Ticking' reports warnings of over 4 seconds (4000ms+). These skipped ticks coincide with the freezing of the framerate.
Steps to recreate are to simply revisit the area of the large cave system of this seed.
Edit: The seed is -994244704 and the area affected is near 82,33,429.
Edit: Found ravine 37,29,416, occurs here as well
Edit: -16,83,162 as well
Edit: Recreated the same world (same seed -> 'xcentrik4') in 14w05b, continue to see "Warning: Clientside Chunk Ticking took XXXX ms"
Related issues
relates to
Attachments
Comments
migrated
migrated
I m having the same problem in my world
migrated
I am seeing this bug also. I am using Gentoo Linux for my Desktop computer and FreeBSD 10-Release for the server. This bug creates huge lag when playing Minecraft. This issue started after I created an new world on my server.
[18:33:43 INFO]: Client> [18:33:43] [Sound Library Loader/INFO]: Sound engine started
[18:33:45 INFO]: Client> [18:33:45] [Client thread/INFO]: Created: 512x256 textures/blocks-atlas
[18:33:45 INFO]: Client> [18:33:45] [Client thread/INFO]: Created: 256x256 textures/items-atlas
[18:33:51 INFO]: Client> [18:33:51] [Client thread/INFO]: Connecting to 192.168.1.2, 25565
[18:38:33 INFO]: Client> [18:38:33] [Client thread/INFO]: Warning: Clientside chunk ticking took 276 ms
[18:38:33 INFO]: Client> [18:38:33] [Client thread/INFO]: Warning: Clientside chunk ticking took 119 ms
[18:38:34 INFO]: Client> [18:38:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 112 ms
[18:38:34 INFO]: Client> [18:38:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 111 ms
[18:38:34 INFO]: Client> [18:38:34] [Client thread/INFO]: Warning: Clientside chunk ticking took 108 ms
[18:38:44 INFO]: Client> [18:38:44] [Client thread/INFO]: Warning: Clientside chunk ticking took 205 ms
[18:38:48 INFO]: Client> [18:38:48] [Client thread/INFO]: Warning: Clientside chunk ticking took 226 ms
[18:39:05 INFO]: Client> [18:39:05] [Client thread/INFO]: Warning: Clientside chunk ticking took 252 ms
[18:39:05 INFO]: Client> [18:39:05] [Client thread/INFO]: Warning: Clientside chunk ticking took 258 ms
[18:39:10 INFO]: Client> [18:39:10] [Client thread/INFO]: Warning: Clientside chunk ticking took 238 ms
[18:39:10 INFO]: Client> [18:39:10] [Client thread/INFO]: Warning: Clientside chunk ticking took 236 ms
[18:39:11 INFO]: Client> [18:39:11] [Client thread/INFO]: Warning: Clientside chunk ticking took 237 ms
[18:39:11 INFO]: Client> [18:39:11] [Client thread/INFO]: Warning: Clientside chunk ticking took 237 ms
[18:39:11 INFO]: Client> [18:39:11] [Client thread/INFO]: Warning: Clientside chunk ticking took 235 ms
[18:39:12 INFO]: Client> [18:39:12] [Client thread/INFO]: Warning: Clientside chunk ticking took 247 ms
[18:39:13 INFO]: Client> [18:39:13] [Client thread/INFO]: Warning: Clientside chunk ticking took 248 ms
[18:39:14 INFO]: Client> [18:39:14] [Client thread/INFO]: Warning: Clientside chunk ticking took 249 ms
[18:39:14 INFO]: Client> [18:39:14] [Client thread/INFO]: Warning: Clientside chunk ticking took 252 ms
[18:39:31 INFO]: Client> [18:39:31] [Client thread/INFO]: Warning: Clientside chunk ticking took 259 ms
[18:39:31 INFO]: Client> [18:39:31] [Client thread/INFO]: Warning: Clientside chunk ticking took 289 ms
[18:39:31 INFO]: Client> [18:39:31] [Client thread/INFO]: Warning: Clientside chunk ticking took 289 ms
[18:39:32 INFO]: Client> [18:39:32] [Client thread/INFO]: Warning: Clientside chunk ticking took 199 ms
[18:39:46 INFO]: Client> [18:39:46] [Client thread/INFO]: Warning: Clientside chunk ticking took 250 ms
[18:41:14 INFO]: Client> [18:41:14] [Client thread/INFO]: Warning: Clientside chunk ticking took 105 ms
[18:41:14 INFO]: Client> [18:41:14] [Client thread/INFO]: Warning: Clientside chunk ticking took 104 ms
[18:42:57 INFO]: Client> [18:42:57] [Client thread/INFO]: Stopping!System information.
[18:33:17 INFO]: Minecraft Launcher 1.3.10 (through bootstrap 5) started on linux...
[18:33:17 INFO]: Current time is Mar 2, 2014 6:33:17 PM
[18:33:17 INFO]: System.getProperty('os.name') == 'Linux'
[18:33:17 INFO]: System.getProperty('os.version') == '3.8.13'
[18:33:17 INFO]: System.getProperty('os.arch') == 'amd64'
[18:33:17 INFO]: Refreshing local version list...
[18:33:17 INFO]: System.getProperty('java.version') == '1.7.0_51'
[18:33:17 INFO]: System.getProperty('java.vendor') == 'Oracle Corporation'
[18:33:17 INFO]: System.getProperty('sun.arch.data.model') == '64'I continue to see this issue.
[23:11:12 INFO]: Client> [23:11:12] [Client thread/INFO]: Warning: Clientside chunk ticking took 101 ms
[23:11:19 INFO]: Client> [23:11:19] [Client thread/INFO]: Warning: Clientside chunk ticking took 113 ms
[23:11:19 INFO]: Client> [23:11:19] [Client thread/INFO]: Warning: Clientside chunk ticking took 115 ms
[23:11:19 INFO]: Client> [23:11:19] [Client thread/INFO]: Warning: Clientside chunk ticking took 114 ms
[23:11:26 INFO]: Client> [23:11:26] [Client thread/INFO]: Warning: Clientside chunk ticking took 104 ms
[23:11:26 INFO]: Client> [23:11:26] [Client thread/INFO]: Warning: Clientside chunk ticking took 107 ms
[23:11:28 INFO]: Client> [23:11:28] [Client thread/INFO]: Warning: Clientside chunk ticking took 369 ms
[23:11:28 INFO]: Client> [23:11:28] [Client thread/INFO]: Warning: Clientside chunk ticking took 350 ms
[23:11:32 INFO]: Client> [23:11:32] [Client thread/INFO]: Warning: Clientside chunk ticking took 340 msThis lags my game for a short period of time so badly it almost becomes unplayable.
migrated
All players on my server are also having the same issues since 1.7.4 through all 1.8 snapshots. We call them the "Laggy Chunks." Causes framerate stutter and sometimes it feels as if the location of the issue slightly shifts.
migrated
We experience the exact same behaviour on our server, using 1.7.5; 1.8 is untested.
From what I've observed, this issue occurs only on "old" chunks. i.e. chunks that were generated way before 1.7.4 - iirc they all were generated (explored) in 1.2
EDIT: The lagy-chunks first occured in 1.7.4 and still exist in 1.7.5
When inside such chunks, the CPU utilization skyrockets on one core, the framerate drops, but the memory utilization (as shown in MC) is no different from normal.
migrated
The map I mostly have experienced this on was started when 1.7 came out and was played with nearly every snapshot along the way.
Still get > 2 seconds of client side chunk ticking in certain areas and it seems to only get worse as the days go on.
migrated
I'm experiencing this on my SSP world generated in 14w02a. However I'm also playing on a server which has some of terrain generated in 1.7 & 1.8 and 1.7 chunks also have this issue.
migrated
I opened MC-55467 today and when a comment said it was invalid I did more research. This is a highly documented issue with timers, dispensers, or water falls, where if the client is just moving out of "render distance" range from one of those active areas, they will experience lag as the game fails to unload the active chunk. This has nothing to do with where you are when the lag occurs. The problem is how far away you are from the source. Change your render distance and you'll see that the problem occurs at that radius from the source rather than where you first experienced the issue. This is 100% repeatable in SSP and SMP in v1.7.5 and 1.7.9.
This is a critical issue if we can't play more than some number of chunks away from another active chunk.
I believe one solution is to teleport away from the active chunk. Everything gets unloaded and the new destination chunk is loaded.
migrated
Hi. I host a private Minecraft server and my players started complaining about client side lag. After much investigation, I finally narrowed it down to this specific bug. It's 100% reproducible and in my map's case the cause was a continually ticking redstone machine. All of CaptainStarbuck comments from May 19 are occurring on my server and describe the client-side reproduction steps and client-side workaround of teleport.
For now, I have disabled the redstone machine as a work-around.
kumasasa
migrated
I just re-checked 1.7.10, verified that the problem exists there, then loaded 14w30c and verified that the problem does NOT exist there. I went back and forth a couple times (resetting each world since downgrading is problematic) and testing slightly differently. It looks to me like this one is fixed.
migrated
I don't think it's fixed. When playing on a 1.8 whitelist vanilla server, I'm still encountering this issue. I sometimes see things like 'Clientside chunk ticking took XXX ms' in the Game Output.