mojira.dev
MCPE-111201

Minecraft is constantly crashing in the same area.

I am getting constant crashes in the same area, the whole game freezes and then crashes to the Xbox dashboard. I have already reported this over 3 years ago (October 2017).

https://bugs.mojang.com/browse/MCPE-28017

I managed to take a screenshot on my Xbox and recorded the co-ordinates where it crashes in the same area.
111, 122, 645
132, 83, 683
114, 97, 725
130, 89, 692

All this has been going on since I entered the beta programme at the time to test the game before it was released to everyone. I was testing the /clone of a large build and ever since it keeps crashing if I enter that area, but sometimes it can be quite a few minutes before crashing again, maybe because it crashes whilst attempting to save in that area.

Linked issues

Comments 24

Would you be able to provide a copy of the affected world? Or even a screenshot?

Here is a screenshot. Crash

Also why does it say Resolved when I have been waiting years for this to be resolved?

When a report is resolved it does not necessarily mean the issue was fixed. It means the report has been processed to a stopping point. When a report is resolved, it is given a resolution, which you can see in the Resolution field under the Status field. "Awaiting Response" is a resolution we use when we have asked for more information from the report's creator. Reports that are set to "Awaiting Response", like this one, automatically reopen when updated.

Thank you for the picture of the build that's causing the crash. Are there any command blocks inside of it that might be generating an infinte loop of activity? Are there any blocks in it that are not currently obtainable, such as something that was only obtainable in an earlier version? Have you been able to successfully clone the original build to other places?

Do you have access to a realm and PC/iOS/Android you could use to transfer the world to device from which a copy could be shared?

It was the build but I moved it years ago when I tried to fix the problem myself because no one was replying to my issue but it is still roughly in the same area. So yes I could clone it, but I tried to go into that area recently which is quite a large area that crashes so I can't do anything without it crashing.

No command blocks are inside that paticular build, and I don't think any blocks that are not currently obtainable are either.

Most the map I build in is safe to do so but quite a large area is off limits, but occassionally I get visitors who wonder into that area and the whole game freezes and then crashes back to the Xbox dashboard.

No I do not have access to a Realm. I have PC Minecraft (Bedrock) though, but I have no idea how to share worlds.

14 more comments

UME is this: https://www.universalminecrafteditor.com/
Note that it is not updated to read chunk data for chunks created in 1.16.100 or later.

I confirmed that the original file you provided still crashes Minecraft on my iPhone in 1.16.221 Hotfix. It's strange that map deletion was enough to make it loadable on my phone, but not on your XBox. Something else that could be deleted, if you want to download UME and try, is player data. The world has hundreds of player data entries (only about 1/3 to 1/2 are unique players, the rest are some kind of data artifact, but that's normal). You can delete all of them except the local_player, if you don't mind losing the inventory, etc. data of everyone who's visited your world. I have not tested if deleting player data alone allows the world to open on my phone.

Another option is to replace the block data in the affect area. If you don't mind losing a bit of progress, you could use a structure block to re-copy the shuttle that's down on the ground over top of the shuttle that's next to the crash area. I tried this by setting the structure block on top of your sea lantern markers and setting the size to 64 x 80 x 64 so that it would replace the air to the east of the upper shuttle where the crashes happen. After doing that, I was able to open the world on my phone and fly around the crash area. Here's a link to that version:
https://drive.google.com/file/d/1kATe-g8rRqfEPcwNYu4wXWBWkAJi-ekh/view?usp=sharing

@GoldenHelmet Nah it still crashes on the Xbox the moment I moved around the bottom back end of the shuttle near the engines 😞. I was starting to think maybe it was my Xbox One that was the issue but I've just got the Series X and still it crashes in that area.

Anything other than the stuff I've built I don't mind being deleted. Isn't their a way to just copy and paste the whole lot into a clean world?

Try this one: https://drive.google.com/file/d/1wA4bpEIkJ5hiSDY7sVGU0YXgFa5aEIL4/view?usp=sharing

Using MCBERepair I found 2 chunks with massive pendingTick buildups, one around 400, Y, 330 (chunk 24, 20) and one around 420, Y, 760 (chunk 25, 47). The latter had a couple of leftover items floating on the ground. I'm guessing that this was where you cloned the builds from, and when you destroyed the old builds it activated observers that were then destroyed before they could complete their deactivation, leaving behind the pendingTick (which is basically an instruction to do a specific block update) which could not be completed. This is related to issues like MCPE-50175, MCPE-50602, and MCPE-64409, MCPE-75966, and MCPE-89260.

After identify the problem chunks I used UME to delete the pendingTick data from them.

As for copy-pasting into a clean world, you can export structures using structre blocks or the structure command on Windows 10, and then use a behavior pack to load them into another world. However, each structure is limite to 64 x 256 x 64, so that would be a tedious process to transfer your whole world that way.

@GoldenHelmet You are amazing, I think you've fixed it. I've been trying to make it crash for about 5 mins in that area and it seems to be rock solid on my Xbox. I want thank you for all your effort and I hope my only world stays fixed.

[Mojang] Mega_Spud (Jay)

We believe this issue is fixed in the latest version.

Edward Pink

(Unassigned)

473157

Confirmed

Xbox

1.16.40 Hotfix, 1.16.200, 1.16.201 Hotfix, 1.16.221 Hotfix, 1.17.34

1.19.10

Retrieved