This is a potential ticking entity error, however unlike Java, we cannot see crash logs to fix the issue. I found the bug when I tried to return to my bed from the end and the game started immediately crashing to desktop. I thought it was an End bug so I used a save editor to move me back to world spawn then walked back to my base. When I was around 300 blocks away my game would crash again, every time.
Tested on current stable release as well as the beta.
This is a relatively new world with not much built besides a very basic villager trading area, some mobs and a zero-tick sugarcane farm. I cannot tell what exactly the issue is without a crash log so I've uploaded my world save for reference. (base coordinates are 592, 69, 464)
Attachments
Comments 2
Thank you for your report!
Crashes and related issues such as these are logged automatically, and will be looked into further by the development team - thank you for your patience and understanding while we get these issues resolved.
If you need help or support you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
It is so obnoxious how games now-a-days dont let us see ANY debug info. like no games have consoles anymore, etc.
This game doesn't have the incredibly useful f3 menu and it doesn't have any logs or anything. Its a trend the industry needs to get rid of.
Allow us to see logs and debug info mojang!