Whenever exploring and loading areas, the game frequently crashes. It did not start like this but recently it crashes every 400-600 blocks travelled. This prevents me from finding anything new in the world or travelling between places with ease. This happens with previously generated terrain and new terrain.
Comments 11
Are there any time frames pertaining to when we can see a resolution to this problem? Being Limited to not traveling more than more than 500 blocks renders the game virtually unplayable. I understand this was recently just reported, but was just curious. Also, is this problem limited to just the beta version or is this across all bedrock console versions?
@Lee,
This only started happening to me in the 1.6.08 release. This is the first time I've seen something that affected game play in such a significant way, apart from some terrible lighting issues that used to happen and sometimes pop up from time to time and connectivity problems with other players.
Under the previous beta 1.6.05 I had a world with a file size of over 400MB mostly due to having to travel many many blocks to find a manor house from a map. That map just corrupted last week and is now unplayable or retrievable. Really pissed about that because my friend and I had put a lot of time into it.
Explorability is the game and if we can't have unlimited sized worlds that are truly unlimited without crashing the game or corrupting the game file then what's the point of having unlimited? In theory its great but I don't think the people at Majong/Microsoft have been able to properly crack the recovery of memory when unloading blocks that are no longer in play. Eventually the game crashes. I've only experienced a few corrupt game files in my many years of playing, but those are usually the critical ones that hurt.
Backup regularly if you don't want to lose what you are working on. It would be great if backups were automatic. It would also be great if we could access local files to restore them if the cloud versions fail, but that's something they refuse to let players do. There it is...
Follow-up to my previous message...
After a lot of roaming around without a map in my off-hand I haven't experienced a crash. If I hold the map in the inventory bar, it seems to work - updating the map, without crashing the game.
Has anyone else that has experienced the unexpected crashing been using the map in the off-hand? If so, try using the map non-offhand and see if that works. Either way, report it here so we know if the map in the off-hand is causing the problem.
Not related to map.
Having a lot of crashes on Win 10 because of this,
with map and without map. Most often when exploring on sea (makes you loose your boat) but also easily reproduced when just travelling on a long railroad.
After experiencing a good amount of play without the problem it suddenly started again and now continues whether I have a map or not in hand or in my inventory. Sigh...
Additionally, experienced a power failure afterwards while playing and lost my map file. Just disappeared from Minecraft. Had a backup but that was 24 hours old so lost a lot. 😞
Thank you for your report!
Crashes such as these are now logged automatically, this will therefore be investigated further by the development team internally.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – 📖 Game Wiki
I do not believe this issue to be resolved as it has happened to me numerous times today. If anything sometimes the memory crashes after only 1450mb when it was almost at 2000mb a week ago when I had commented on this issue. Can we get clarification that this has indeed been fixed for xbox console please.
I think the status of this thread needs changing from resolved as it is still happening yesterday alone was crash after crash, sometimes i would only move like 5 blocks from where i was and it would crash.
Being on a boat or rail cart when the game crashes results in you loosing your cart or boat . Makes it hard when your just starting out and loose the iron you have got through the crashes
Seems to be a memory issue. Whenever the total mem gets close to 2000 it crashes. Worse when two players are in the world. Only started after 1.6.08 update and happens consistently, making exploring and moving more that 500 blocks challenging as the mem starts getting consumed.