Not too long after updating to v1.13 I get an error "You are out of local data storage and unable to save your progress." Reloaded my world and got the same error again. I have plenty of local storage and this has only happened since the new update.
Linked issues
duplicates 1
Attachments
Comments 16
I was in a boat too and upon reloading I was sinking in water. I ended up going to an island and saved. Literally unplayable in this world for me till this is fixed.
Since the 1.13 update I have started seeing this problem. I built a world in 1.12 and have never had this issue, but immediately after the update it started. I run a very clean game, with no mods or anything. Some data:
World size: 1.5 Gb
C-drive free space: 670 Gb
Mods: none
Skins: MC standard
Neither Disk usage, CPU nor GPU are overloaded at the time of crash; I keep task manager open and don't see anything that would cause a crash. I do notice that it crashes right after the game saves (the chest appears in the upper right corner to indicate the save). And it usually happens after I have seen it save the game 2 or 3 times, which makes me believe that it is linked to saving the game to the C drive, but perhaps there is a disk cache problem which causes the issue.
Graphics settings don't have an impact; I ran the game with all sorts of settings and no problems. The game crashes even when I am AFK, just standing in my house doing nothing (with very low RAM and GPU usage). It crashes when digging a mineshaft, it crashes while flying around, while putting blaze rods in a minecart, etc. The common theme is always the game saving to the hard drive.
As this bug appeared right after installing 1.13 with exactly the same world as I had the day before (in 1.12), I have reason to believe this update has a flaw in how it saves files to disk.
I too was in a boat in the middle of a large nearly world sized body of water. Not fun! I didn't notice the chest but I often multitask while playing and missed it. My world is 3.9 gigs, but I have over 700 gigs available on my C drive, and I also checked my task manager and nothing is out of whack. I've been playing this world since July 2017 and it's survived two very large updates (Update Aquatic and Village and PIllage" and very few hiccups....now this? I just wanna hunt down some foxes...you know?
I uploaded a pic of the error message, there is also a variation that shows earth tones in the background...I've gotten both.
Still here. Still crashing after about 10 minutes or traveling a small distance, whichever comes first. My Son is heartbroken.
Similar/related: Issue
Many communities are experiencing this same issue. The host will see an error indicating it is our of space, and players will see an error saying the world is corrupt.
The community seems to be in agreement that it is related to loading new chunks, which is why it happens most often while traveling long distances, like with a boat.
There is already a bug report higher up in the priority list(90 Votes+). You can help draw some attention to our problem by voting for it & adding any additional details you may have. Hopefully by consolidating and raising awareness of the one issue will receive a faster resolution.
https://bugs.mojang.com/browse/MCPE-32501
Thank you for your report!
We're actually already tracking this issue at MCPE-55010, 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.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This looks like a classic "memory leak". I have gotten this several times today. On shutting down and thin restarting Minecraft, and selecting my same world to play, it will start me up close to where I was when it failed. Several times I had been using a boat and upon restart found myself without the boat near and floundering in the water. I can then play for a while before getting the same error message.