Please see explainer video: https://youtu.be/8EYrVxP6sA4
Various chunks around the world are "corrupted", "broken", "slow", "laggy" where redstone does not fire properly and water does not flow properly.
Redstone becomes extremely slow, with a delay of several seconds before it activates and water flows extremely slowly.
This can happen in 1 chunk next to another chunk which is completely fine.
Removing farms, redstone, hoppers and pistons in the area does not improve anything.
Render distance is on minimum, mob spawning is off, no command blocks active and all entities have been wiped from the world.
Toggling the difficulty to peaceful and using commands to kill all entities in the loaded areas does not fix the problem.
The problem is not due to lag as the chunks next to the corrupt chunks work as expected.
This happens on Minecraft Bedrock single player worlds and Minecraft Bedrock Realms.
This is currently affecting version 1.12.0 across all devices.
Related issues
relates to
Comments
foxynotail
migrated
Hi,
I went though my world file with a custom script.
I have 15 chunks that have more than 1000 pendingTicks all of them being from kelp blocks. All those chunks have the same redstone issue.
I might be able to extract one of those chunk and attach it to this ticket if you are interested.
migrated
This bug is literally bringing realms down.
Steps are easy to reproduce :
- Create an new world
- Load ocean chunks with kelp in it
- Wait... (To speed up the process you can increase randomTickSpeed)
At any point you can take a look at the nbt data of that chunks to assess the amount of pending tick that will never be removed, but still be simulated every tick by the server.
When the numbers get too high the server starts to lag and end up crashing.
Auldrick
Lag caused by kelp growth was reported fixed in 1.14.0. If you still experience problems with pending chunk data accumulating in association with kelp growth, please comment below so we can consider whether to reopen this ticket. If you experience problems with pending chunk data associated with some other process, please create a new report describing what you know about it.
migrated
I am experiencing this in v1.14.20 on Windows 10 (UWP).
migrated
(Tested before reported - from 'Technical Bugs List' https://docs.google.com/document/d/1nziKYzCr4pBdCRj2gIMlfr9MVdWHd6HyafdiBHx9F0c/edit)
This issue happens in 1.14.30 hotfix and 1.15.0.51 also.
Auldrick
@unknown: This issue was found to be caused by incorrect handling of pending chunk data in some chunks where kelp was grown. That problem has been fixed and the fix was confirmed by the original reporter (Foxy No-Tail) in a video on YouTube. So apparently, your testing is either exposing a different cause of the same problem or is identifying an entirely different bug, in which case we'll need you to create a new ticket for it. Before we can decide whether to reopen this ticket or ask for a new ticket, we'll need more information about exactly how you're testing.
In fact, for all these issues that you re-test on every release, knowing how you tested it would be very helpful, because having multiple ways to reproduce the problem narrows the space within which the developers have to look. I'm not asking you to describe your test every time you give us a comment with additional affected versions, but it would be appreciated if you would describe it once. It would also confirm that we're all talking about the same bug, not similar bugs with different causes.
migrated
Hi. I made a mistake here, you are right.
I want to say I test everything before I report and I don't want to describe you more than that to prove because I know it's true.
The way I report is - first of all I test all the bugs in the list I mentioned and then report them in batches one after one.
I just forgot to delete this from my list, probably missed the notifications on my Email.
I know you just do your job but mistakes happen sometimes...
Update: I have discovered a way to "fix" the issue, per chunk, using Universal Minecraft Editor to edit the LevelDB file.
Tutorial in this video here: https://youtu.be/BTD-6rua5sQ
Basically, load up the chunk that is lagging, delete the PendingTicks data.