After switching to 1.17.32 version, my super flat world started to take up to 20 GB of RAM, it also started to run for too long.
I set the chunks to 16 (instead of 80), but it didn't help, the game still requires up to 20GB of RAM (there are 24 on my device)
Previously, this world didn't work because of error MCPE-140428
Linked issues
is duplicated by 17
relates to 2
Attachments
Comments 31
Additional comment - on the XBox, I'm seeing invalid chunks as a result of this behavior, which exacerbates the problem the next time you try and open the world.
Similar. Bedrock, Win10. My survival world (a Realm) that's only ~80MB is taking up dozens of _Giga_bytes in memory and takes forever to both load AND save on exit.
When I'm in the world there is significant lag; every couple of minutes, I have to wait 10-20 seconds for the last several actions to take effect.
This is true on Realms AND locally. I have gone through the Realms backup history, downloading the worlds and playing locally, and it is appears to be the1.17.32 update. Every world through 1.17.31 is fine; the moment it goes to 1.17.32, they start having problems.
Notably, the memory leak/spike seems to get worse over time... the more times I load the world, the bigger the memory spike and the longer it takes to load.
Also, one of these backups that I downloaded has now ballooned to a file size (as displayed in the game menu) of 682.0MB, though not all of the files have had that effect. And worth noting that a couple of other local worlds that are <10MB, do not appear to have this problem. So far, it's just the 1.17.32 worlds I've downloaded from the Realm.
Notably, the memory leak/spike seems to get worse over time... the more times I load the world, the bigger the memory spike and the longer it takes to load.
I saw this in my testing yesterday; 21MB world using BDS took more memory each load, eventually consuming 28GB.
Here's an example world affected by this problem: https://drive.google.com/file/d/1bXnMAFmXI74eYFcT2WWurFwDbVk2t1Cx/view?usp=sharing
Compressed ~90MB
Uncompressed >600MB
Uses ~20GB memory
Very long load and unload/save
And very laggy
However, couple things to note:
The log file at db\lost\025701.log accounts for essentially all of the uncompressed file size.
Only one of the .ldb files (db\025713.ldb) has a substantive discrepancy between compressed and uncompressed size...
So on a wild guess (and many other tests), I simply deleted both of those files, re-imported to Minecraft, and the world runs perfectly both locally and on Realms on both PC and Switch: no lag, no long load time, no memory spike, and all of the data is there so far as I can tell... (though presumably that filed contained some kind of relevant world data?)
I am still testing with multiple reloads of the world, and presumably if this issue happened once, it could certainly happen again... but the above still seemed useful diagnostically and as a short term fix.
This was fixed in 1.17.41 according to the changelog
Loaded 1.17.41 onto the XBox and tested out a world that was affected by this. I didn't stick in there long, but I was able to do far more than I was able to previously. So, initially at least, it appears to be resolved.
Similar issue here with a relatively small Skyblock map (this map: https://mcpedl.com/classic-skyblock-plus/. I'm running a few versions of this in different environments (Xbox, Android, BDS), and I'm seeing this same issue.
One version I'm running on Bedrock Dedicated Server on Linux, and you can watch the memory usage in htop spike as you load the map, then spike again when someone connects. And by "spike" I mean a 21MB map takes up 2.5GB of RAM to start, spiking up to 4-6GB when someone joins. After that user logs off (or you restart the server) BDS takes forever to start as it's consuming all the memory on the box. Usually the OOM kill (out of memory killer process on Linux) will kill BDS after it's consumed all the memory and all the swap space.
I believe this memory leak is happening on the other platforms, but I don't have the tools to monitor it, especially on the Xbox. If those systems have an OOM killer (Android does at least), then you'll see Minecraft just die immediately, due to the corrupt world eating all the available memory and swap.