19+ GB of RAM in worlds

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.

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.

I would like to confirm the same issues as reported on this thread, cant add anything much different to help except my situation is Windows 10, i5 7400 @ 3.00 Running BDS versions 1.17.32 has the same issue, upgraded to 1.717.33 and still have the same RAM issue,

when launching the world it almost instantly consumed 14/15gb of  my 16gb RAM just opening the world with BDS, it takes some 10 minutes to complete the server launch at which point RAM fluctuates back to about 9-11gb. while logging into the world to play the RAM increase back to 14/15gb.  then settle back to 9-11gb.  while in the game loading new chunks takes several minutes and again RAM continues to max out and idle back to about 75% load. chests taken about 30 seconds to register opening if at all, blocks can take up to a minute to break etc or then not.

Text chat is delayed by several minutes, and text is often grouped not back n forth.

Exiting BDS console using STOP takes forever, even longer than the original loading, then the RAM count drops steadily down to less than 1gb over about 15 minutes, twice from about five or six times i had run some tests I then heard my PC noise pitch change suddenly and the RAM just climbs back up to 11gb, it seem like as it was about to close it looped back to running again. this hasn't happened every time but was odd seeing it at all.

 6 Oct 2021 mojoang released 1.17.34.02 - I can confirm the RAM issue persist in this version update.

Hmmmmmm... I don't seem to have this issue on my laptop and my laptop is a 2016 or 17 HP i3 intel core, Minecraft runs fine.

I play on a bds and the lag is soooo unforgiving since the update it’s crazy.older worlds before the update do  not have this problem. All settings are as low as it goes but the main pc is higher than it need to run a bds so no issues there. Please fix this so we can play the dang game mojang, runni got on a legion pc with an intel core i7 with 2.6 GHz and a 16 GB RAM graphics is an invidia  RTX 2060, this is the only game I currently have on it.

So I have been building a world with my friends for months. Working on custom behavior and resource packs. All that stuff.

Only after the most recent update 1.17.34 did we begin to have issues. It started as small lag and some teleporting of players. Then increasingly slower saving & opening of the world. I then noticed that the world size, which started at about 25MB, then it went up to about 200+MB randomly. This all happened within 15 minutes or so.

I then tried to open the world again, and about 20 minutes later it finally opened. The game was unplayable, it was basically frozen, and then about another 20 minutes later I was able to save & exit the world. At this point the file said it was 599.60MB in size.

Right now the world says 25.6MB in file size, but I am unable to open the world at this point. I get stuck on the Loading Resource Pack screen. And all this seems to follow the same examples listen by others. I have attached some screenshots of my issues where my RAM is pretty much capped max. (Screenshot1 and Screenshot2) Note: I had nothing else open at the time and I only have this issue with Minecraft. I hope this gets fixed very quickly!

This is similar but isnt to do with the log file

https://bugs.mojang.com/browse/MCPE-144052

I would like to add that I am able to play and download packs on Minecraft pocket edition on my iPad. . . .I have noticed a lot of lag and even some rubber banding back to the position I started in, even if it’s across the map. . . .but it works & allows me to download packs & skins. . . .

  I am able to play vanilla (no packs or skins) on my ps4 but can not download packs or skins due to Minecraft claiming there’s no available space (I have over 300gb available on the PlayStation & only have one or two vanilla worlds on Minecraft).

  I have come to this ticket because it was suggested to on another ticket (specific to not having available space, even tho we all have available space). . . . .

I find it strange that the iPad version isn’t have the same problems. . . Only the lag & the rubber banding. . . . .

I am one of Yash"s builders.  I saw first hand it going from fine to unplayable.  I have uninstalled the game until this is fixed.  

My ps4 is what I am building on, I only have 3 vania worlds, I have 500gb + on ps4 and only using a tiny portion on my MC though right now not at all because if this is a memory or code leak I do not want THE GAME affecting the HD.  I seriously think this needs to be addressed.  

And not with a condescending tone that I have seen recently on other tickets that is not in character of Mojang.  

Users talking about the issues are them sending more information as it becomes available.

I should not have to fear sending more information when those in the community are working through things.  I also should not have to delete MC because none of these questions are being addressed and my brand new ps4 is severely struggling.

Please help and thank you, criticism does not mean I am against you, it means I care about this game and the community.

I been recommended this ticket and I have noticed that my ps4 was struggling it's old my friends and I are making a realm I'm one of the builders the host being on PC stated that the hard drive is maxed out same with ram my hard drive has taken a great deal more damage this is a serious bug damaging systems imagine how bad switch or mobile is getting impacted I had to delete the game to save my system it seems to effect even when it's not directly running I love this game I been playing since it's 1st port to PS3 I know it will be fixed it has to be unless you want replace our machines. This is the 1st time I seen Minecraft get a blowout being unplayable even the hotfix 1.14.6 wasn't this bad it was laggy but didn't fry our hardware.

The title of this report is suggesting that this is affecting flat worlds - can you please confirm if this issue is affecting all non-flat worlds?

Yes, this bug works on regular worlds too. My world weighs 300 mb, and after some action crashes and weighs 400mb.

It effects my 690.4mb regular world

@Mega_Spud The world I am building on is a superflat with previous poster @Yash.   Tho I have seen posters on other tickets and this say it affects regular worlds as well.

Ty 

Exactly the same issue that i've been experiencing. This lag happened after the 1.17.34 update.

I can't open my main world or its copy ( i have to wait for several minutes before it will load but most of the time it will just hang). The RAM usage reaches to 99% while loading my main world. Also the file size of my main world keeps changing (from 75mb to 300mb to 600mb to 75mb again). 

There is no problem in generating the world in the newly created world or other world. The RAM usage is stable at 35~40%. The file size is normal. 

Mine is regular world - Survival. 

Im using PC Win10.

Thanks

Been doing experiments and this bug is tied with multiplayer if using a backup with no other players the world seems to be stable however if anyone joins the world starts slowing down degrading almost instantly when closing and reopening the file size doubles again and almost all ram and hard drive is used this bug is caused by multiplayer 

My world is having this problem but I'm alone

 It is taking to long to resolve the issue. May we know the status of this issue/bug?

Even this latest update, 1.17.40, the issue still exists.

Well, I had a workaround - using My Files Explorer on the Xbox, navigating to the Minecraft worlds, copying it to a USB drive, then using Amulet editor on a PC to copy the world to a new, blank (cleared) copy of the world, then copying it back to the Xbox.  It worked great, though I'd have to repeat the steps every couple of days.

Sadly, the latest Xbox update completely broke My Files Explorer.  It can see neither USB drive, nor the com.mojang folder on the Xbox.  Thanks Microsoft! 

So, to echo my fellow sufferers...any progress?  Anything we can provide to help isolate the issue?  Any workarounds?  Anything at all?

Just an update: the PC workaround I posted above is still working.  We've played many times on that Realm/world without issue (on both PC and Switch) since I implemented that fix. (Though never did figure out what the heck 025713.ldb corresponded to...)

I'd be curious if other PC users have attempted something similar (harder for console users); all you need is an archive viewer/editor.  If you have tried it, did you also notice the log file was massive?  Were you able to identify any unusual .ldb files?

Just fyi, I also disabled a custom texture pack (https://bedrocktweaks.net/resource-packs/), but I'm doubtful that played a role...

(And here are specs, which I hadn't posted before...)

• Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz

• Memory 32.0 GB, Speed: 2133 MHz Slots used: 4 of 4 Form factor: DIMM Hardware reserved: 40.1 MB

• Samsung SSD 970 EVO 500GB, Capacity: 466 GB Formatted: 466 GB System disk: Yes Page file: Yes Type: SSD

• Radeon RX 570 Series, Driver version: 26.20.13002.133 Driver date: 8/27/2019 DirectX version: 12 (FL 12.0)

• Windows 10 Education Version 21H1, OS build 19043.1288, Experience Windows Feature Experience Pack 120.2212.3920.0

I play on pc (windows 10,16 gb of ram, ryzen 5 3600) and i'm having the same issue, my world is randomly jumping from 30% to 80% ram usage, and my worlds file size went from 10mb to 300mb without me loading in any new chunks. every time I attempt to join the world the file size increases and so does the loading time. ive tried creating backups and going on an older copy of my world but the issue still happens, hopefully theres a fix for this soon.

I have this problem too, I've not been using Minecraft for several weeks but just came back to it. I'm using a small HP Elitedesk mini G1 with 8GB ram running a bedrock server on Ubuntu server 20.04. RAM usage has always been fairly minimal, but recently the RAM usage rises steadily until stable at 7.4GB, when I then try to connect with either my PC client or from Android, the server crashes with the last entry in the log reading '<user> connected'.

I restored an earlier backup of my world and was then able to connect, but when I disconnected and then tried to reconnect the server crashed again and every time afterwards.

This sounds close to MCPE-124058, however this issue is only high RAM, not high CPU or GPU like MCPE-124058. The two may be related.

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.

Up until now seems like the new hotfix fixed it! Will keep you guys posted!

Did not get the updated Jet for Nintendo switch still wating

This also happened to me also in flat world it taking up my Memory I have 16GB and takes 99% Of it Until he loads in it's a like void world blocks don't render but on this update it's fixed