Unable to open world saves (but able to create new worlds and play in those)
This ticket is being used to track issues around crashes that occur while in or approaching the new villages and subsequent crashes when reloading the world. The tickets linked as duplicates have a variety of descriptions but all involve crashes at villages and we believe they have the same underlying cause.
In 1.11.0.4, the game sometimes crashes while a player is in a new village or is approaching one. This happens in both worlds created in 1.11.0.4 and worlds upgraded from earlier releases, and both with and without Experimental Gameplay enabled. The villages can be new V2 villages or V1 villages that the player has been manually upgrading for V2 villagers. There are some indications that certain workplace blocks may be involved, but this is not well established.
The bug appears to be triggered at random, because in some cases these villages have been visited multiple times prior to the game crashing. Once triggered, some worlds crash the game every time you attempt to load them, but there are also cases where you can reload the world after it crashes and it doesn't crash again until you return to the village.
I have attached test worlds. "Ad hoc bug testing 1.9" was last opened in 1.9. "Ad hoc bug testing 1.11.0.4 crashed" was imported from the 1.9 world, then opened and explored until the crash happened (with the player at about -1300,90,-450).
Steps to reproduce:
- Import Ad hoc bug testing 1.9.mcworld into 1.11.0.4 Beta. You should spawn at world spawn, about (600,72,0).
- Go to the command blocks and press the button on the center one, labeled "to village". This takes you to an old village whose villagers have been converted but no work as been done to upgrade the village.
- Fly up to about Y=90, then fly east to about X=1307.
- Sprint fly south to about Z=-350. You see a village ahead of you. You might crash as you get close, or you might not crash until after you pass over the village. If you don't crash by Z=-500, start over, as the bug is apparently triggered randomly.
If you can't get the bug to trigger, it might be worth trying on a device with less memory available or a less powerful graphics processor.
Original description:
Opening a world (from the same beta 11.0.0.4 version or any previous versions) will result on a crash. It'll show the usual loading world screen but it's just crashes once it's done loading.
Creating a new world will not result in a crash but after closing and trying to reopen that same world, the game will crash once again.
Reproducing the bug is really easy to do since all you have to do would be to try to open a world on Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
Linked Issues
is duplicated by12
MCPE-42980crash issueDuplicateMCPE-42983Anytime a custom village is made, when the villagers go to sleep, the world corrupts.DuplicateMCPE-43018Game Crash while loading a worldDuplicateMCPE-43024New Village CrashingDuplicateMCPE-43026crashing in New beta 1.11DuplicateMCPE-43031CrashingDuplicateMCPE-43046Crash when riding horseDuplicateMCPE-43048Crashes when I open my worldDuplicateMCPE-43086Villages Lag too muchDuplicateMCPE-43087Game crashes when loading a world.DuplicateMCPE-43106Village CrashDuplicateMCPE-43123Being in a village crashes my gameDuplicate
- Fixed
Hiram Chavez- 13
- 11
- Confirmed
- 184121
- Android
- Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
- crash jobsite-block lag village workplace-block world-loading
- 1.11.0.4 Beta
- 1.11.0.5 Beta
Created Issue:
Unable to open world saves (but able to create new worlds and play in those)
Opening a world (from the same beta 11.0.0.4 version or any previous versions) will result on a crash. It'll show the usual loading world screen but it's just crashes once it's done loading.
Creating a new world will not result in a crash but after closing and trying to reopen that same world, the game will crash once again.
Reproducing the bug is really easy to do since all you have to do would be to try to open a world on Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
- Unresolved
- Open
- Unconfirmed
- Android
- Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
- 1.11.0.4 Beta
is duplicated by
This ticket is being used to track issues around crashes that occur while in or approaching the new villages and subsequent crashes when reloading the world. The tickets linked as duplicates have a variety of descriptions but all involve crashes at villages and we believe they have the same underlying cause.
In 1.11.0.4, the game sometimes crashes while a player is in a new village or is approaching one. This happens in both worlds created in 1.11.0.4 and worlds upgraded from earlier releases, and both with and without Experimental Gameplay enabled. The villages can be new V2 villages or V1 villages that the player has been manually upgrading for V2 villagers. There are some indications that certain workplace blocks may be involved, but this is not well established.
The bug appears to be triggered at random, because in some cases these villages have been visited multiple times prior to the game crashing. Once triggered, some worlds crash the game every time you attempt to load them, but there are also cases where you can reload the world after it crashes and it doesn't crash again until you return to the village.
I am preparing sample worlds to be attached soon.
Original description:
Opening a world (from the same beta 11.0.0.4 version or any previous versions) will result on a crash. It'll show the usual loading world screen but it's just crashes once it's done loading.
Creating a new world will not result in a crash but after closing and trying to reopen that same world, the game will crash once again.
Reproducing the bug is really easy to do since all you have to do would be to try to open a world on Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
is duplicated by
is duplicated by
This ticket is being used to track issues around crashes that occur while in or approaching the new villages and subsequent crashes when reloading the world. The tickets linked as duplicates have a variety of descriptions but all involve crashes at villages and we believe they have the same underlying cause.
In 1.11.0.4, the game sometimes crashes while a player is in a new village or is approaching one. This happens in both worlds created in 1.11.0.4 and worlds upgraded from earlier releases, and both with and without Experimental Gameplay enabled. The villages can be new V2 villages or V1 villages that the player has been manually upgrading for V2 villagers. There are some indications that certain workplace blocks may be involved, but this is not well established.
The bug appears to be triggered at random, because in some cases these villages have been visited multiple times prior to the game crashing. Once triggered, some worlds crash the game every time you attempt to load them, but there are also cases where you can reload the world after it crashes and it doesn't crash again until you return to the village.
I am preparing sample worlds to be attached soon.
Original description:
Opening a world (from the same beta 11.0.0.4 version or any previous versions) will result on a crash. It'll show the usual loading world screen but it's just crashes once it's done loading.
Creating a new world will not result in a crash but after closing and trying to reopen that same world, the game will crash once again.
Reproducing the bug is really easy to do since all you have to do would be to try to open a world on Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
This ticket is being used to track issues around crashes that occur while in or approaching the new villages and subsequent crashes when reloading the world. The tickets linked as duplicates have a variety of descriptions but all involve crashes at villages and we believe they have the same underlying cause.
In 1.11.0.4, the game sometimes crashes while a player is in a new village or is approaching one. This happens in both worlds created in 1.11.0.4 and worlds upgraded from earlier releases, and both with and without Experimental Gameplay enabled. The villages can be new V2 villages or V1 villages that the player has been manually upgrading for V2 villagers. There are some indications that certain workplace blocks may be involved, but this is not well established.
The bug appears to be triggered at random, because in some cases these villages have been visited multiple times prior to the game crashing. Once triggered, some worlds crash the game every time you attempt to load them, but there are also cases where you can reload the world after it crashes and it doesn't crash again until you return to the village.
I have attached test worlds. "Ad hoc bug testing 1.9" was last opened in 1.9. "Ad hoc bug testing 1.11.0.4 crashed" was imported from the 1.9 world, then opened and explored until the crash happened (with the player at about -1300,90,-450).
Steps to reproduce:
- Import Ad hoc bug testing 1.9.mcworld into 1.11.0.4 Beta. You should spawn at world spawn, about (600,72,0).
- Go to the command blocks and press the button on the center one, labeled "to village". This takes you to an old village whose villagers have been converted but no work as been done to upgrade the village.
- Fly up to about Y=90, then fly east to about X=1307.
- Sprint fly south to about Z=-350. You see a village ahead of you. You might crash as you get close, or you might not crash until after you pass over the village. If you don't crash by Z=-500, start over, as the bug is apparently triggered randomly.
If you can't get the bug to trigger, it might be worth trying on a device with less memory available or a less powerful graphics processor.Original description:
Opening a world (from the same beta 11.0.0.4 version or any previous versions) will result on a crash. It'll show the usual loading world screen but it's just crashes once it's done loading.
Creating a new world will not result in a crash but after closing and trying to reopen that same world, the game will crash once again.
Reproducing the bug is really easy to do since all you have to do would be to try to open a world on Huawei Mate 10 (ALP-L09) EMUI 8 (Android 8)
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
is duplicated by
@[MCPE Mod] Auldrick: since you removed my post, does that take away my vote and stop watching?
[MCPE Mod] Auldrick, because you are removing (aka hiding) my posts, you do not want me posting bug reports? If this is the case, then I will delete all my bug reports in JIRA. I thought you welcomed Minecraft user input, but it appears not to be the case. I did not post what I discovered in testing the current crash issue to the Minecraft Wiki or Discord, because of your advice. But that will now be remedy. Have a nice day
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
I'm glad to hear that the issue may be fixed for some people. However, the developers haven't yet notified us that they have fully resolved the problem, so we will keep this ticket open until they tell us they're done. Meanwhile, other people may continue to experience crashes.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Thank you for your report!
We're actually already tracking this issue at MCPE-42953, so we will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
I think this is the same as MCPE-42953
Is this still happening in the 1.11.0.5 Beta release? If not, this was probably the same bug as MCPE-42953.
Otherwise, crashes such as these are reported automatically and handled internally by the developers. Feel free to add any additional information here that you think they might need.
This ticket will reopen automatically when you reply.
@necrolyte
MCPE-42953 is 1.11.0.4, this bug report is 1.9.0.
Check the versions before commenting.
There are many similar reports coming in about crashes that start when approaching or inside a village. In one case a fletching table has been implicated as the cause. Often, the game crashes when trying to reload the world.
Were you able to open these worlds once, but crashed on later attempts? If so, were you in or near a village when you crashed?
After taking into consideration that something with villages is the cause of the crashes, I decided to test it.
Doing some quick tests in the seed "Chepo", I can confirm it has something to do with villages. I was able to generate a new world, actually load into the world, close the world and reopen it right at spawn (I didn't move from spawn).
I was able to reopen the world without problems but after going east about 200 blocks to the nearest village, I decided to look for fetching tables before closing and trying to reopen the world, found no fetching tables and it still resulted in a crash.
It's not the fetching table causing the crash but it has to do something with being in/near a village
After doing some more tests with the same seed/village. I have come to the conclusion that the grindstone is the one causing the crashes.
Generated the same seed, broke the cauldrons, closed the world and trying to reopen the same world resulted in a crash.
Tested the other work blocks that villagers use as well.
Doing the same thing but breaking the only grindstone in the village resulted in a success. I was able to reopen the world after breaking it.
Thanks very much!
In my own case it was a world I use to test bugs. I had opened it for testing many times, and had been to the village in 1.11.0.3, but when I got near it in 1.11.0.4 I noticed a "church" (village temple) was only half generated, and after a moment I crashed. Since then I can't open the world any more. But if I re-import it from the 1.9.0 backup it's fine as long as I stay away from that village. I have a different village I can visit without crashing.
Edit: After further experimentation, I don't believe it's related to a workplace block after all. I had crashed several times while flying in creative to one village. After re-importing the world I decided to try walking into it and it didn't crash. I spent the entire day standing near a blacksmith working at his grindstone, and it still didn't crash. I think the crash may be caused by a random event that happens while the game is loading chunks that contain a village, since all my crashes happened while I was flying toward it from different directions. Possibly the higher speed of flying means I got near the village before the game had time to finish loading the chunks and that caused the crash somehow.
Been studying for exams since those are coming up but I realized that what you said is right after some testing though I didn't have time to respond right away.
Some random events that occur in the village when in loading at different speeds does seem to be the cause of some of the crashes but I still have to say that the some of the workplace blocks have to something about it or are a different cause of crashes.
Like I said during in the conclusion of some of my tests,
"After doing some more tests with the same seed/village. I have come to the conclusion that the grindstone is the one causing the crashes.
Generated the same seed, broke the cauldrons, closed the world and trying to reopen the same world resulted in a crash.
Tested the other work blocks that villagers use as well.
Doing the same thing but breaking the only grindstone in the village resulted in a success. I was able to reopen the world after breaking it."
The only way I was able to reopen the world was by breaking the grindstone beforehand.
Fortunately, it's not up to us to figure it out. The facts we've each experienced are on record here for the developers. That's all we can do, and all we need to. Thanks for all the effort you've made to help us understand this problem!
THIS PROBLEM IS CONFIRMED TO NOT BE CAUSED BY WORKPLACE BLOCKS. BEING IN THE VILLAGE IS FINE. IT IS WHEN SOMEONE ALLOWS A VILLAGER TO SLEEP IS WHEN IT CRASHES. I made 6 custom village worlds and had 4 villagers in each as a control. They all were these professions: Tool Smith, Cartographer, Farmer, Librarian. I set the time to night, when the librarian went to sleep, the game crashed. I did this FOR ALL OF THE WORLDS and the game crashed. So I have found the reason. Any villager who sleeps crashes the game unless it is a nitwit, they sleep all day and its fine for them. Please, thank you all for trying.
JAL: Your experience doesn't match everybody's. For example, I personally can reproduce the crash using a 1.9 world I've imported with the day/night cycle disabled and the time set to noon, so there is no sleeping involved; All I have to do is fly over the village. There are many other reports linked to this that don't mention sleeping as well. I have no doubt that in your case sleeping can trigger the bug, but it isn't the only way to trigger it, and workplace blocks cannot be ruled out as another way.
A village I made in one of my world doesn't crash when there's no work station blocks, but does crash when there is and villagers start their work schedule. Sleeping villagers haven't cause any crashes for me so far.
This also only affect my LG Stylo 4 (Android 8.0) but doesn't affect my Nvidia Shield TV (Android TV 8.0)
Edit: It also affects the Nvidia. When using my LG to join the Nvidia via LAN, the game crashes when the LG player is getting closer to the village with work station blocks while villagers are working. The LG player is able to go to the village sometime after noon when the villagers are socializing and at night when they're sleeping
I'm also experiencing world-corrupting crashes in worlds where I have never entered a village, seemingly at random.
Kayla Huskey: I don't think you have to actually enter a village, just be near enough to load its chunks. Could you have been at least close to one? If not, you either have a different problem or this problem is even less well defined than I hoped it was.
In one of the cases, I was in creative and used /locate to find a village, and it was within 150 blocks. In the others, I'm not sure. There may have been villages near me that I just hadn't reached yet.
Happening to me on a new village that only has composter & stone mason blocks in it, 1.11.0.4
I just tried the attached world, I got to the village fine, but as soon as I started to fly around it... well, here I am.
cameron c: The bug tracker doesn't have a private message feature, since it isn't intended as a general discussion forum. The workaround you discovered previously that allowed the app to load doesn't make sense for this bug, which happens after the app is running. It's also risky and shouldn't be thought of as a magic bug bullet that people should try shooting at every problem, just in case.
I'm 95% sure it's something to do with villager AI or inventory. Started getting crash on map load went in and wiped all the villager nbt data except there location. And map opens like a charm
On my end, this issue appears to be resolved in
1.11.0.5
This does appear to be fixed in the latest issue, and the attached test world no longer crashes after launching.
I'd suggest for any other crash related issues that a new ticket is created with an attached world save so the issue can be reproduced.
Sounds good for my old saved game. Now it opens correctly in 1.11.0.5.
The new update (1.11.0.5) caused even more lag for me. The game now crashes every time I get near the villagers. I can't even kill the villagers to prevent it