World corrupted/broken in 1.18.30

I just posted the exact same issue sadly 😞. Is there any chance you went beyond your previously generated world and generated new chunks after updating? I suspect that's the cause on my end, since they changed world seeds in this update.

Yes, I just went into new chunks that weren't yet explored to build a farm there. Then I returned to my old base and all the trouble started. Luckily I do have backups but this issue is a pain and now I'm afraid to load any backups in the 1.18.30 version.

As I described the world only freezes when I go into a certain area, that area is old tho and was loaded years ago. To me it seems like a corrupted chunk or something that freezes the world as soon as you go there. 

Yeah that checks out exactly with my experience. Going back to an older version isn't an option because most of my friends play on Switch, so I really hope this can be fixed...

After reverting to a backup from before I went exploring the freeze still happens at the exact same spot on my minecart track. I even spawned in a whole different place and it still only froze right there. I think there might be something to your corrupted chunk theory. Perhaps the fix is just bordering off a restricted area for players haha

After 1.18.30 update I registered very large dificulties open my survival world.
80% of the times it gets an error at "creating terrain", and closes the app.
When sucessfully enters, after few minutes the game cracks and closes.
I managed to create backup vesions of the map, but all have the same issues.

I'm on nintendo switch version.

I've managed to upload the world to Realms and seems to be working fine on PC version.

On nitendo switch, some test and lighter (creative) worlds seems to go ok. 

I just loaded a backup of the world from before the 1.18.30 update and before i went exploring. The issue isn't present in the backup. I went to the broken area and nothing freezes or lags.

@unknown, since the world is too large to attach, you can upload the world to OneDrive or a similar file-sharing site, and then share the link.

Is it possible to share the download link with a mod directly so not any stranger can download it?

I did some further testing in the corrupted world. Every time i load into the world it works for about 10 seconds until everything freezes and chunk loading stops. The world doesn't crash tho, I can fly around in the already loaded areas but no interactions or anything works. Meanwhile I left the world open like that for a bit and in the task manager it kept piling up more and more ram, I'm certain it would have crashed the game sooner or later if I left it open.

You can set the security level of this ticket to private and share the download link in a comment. I will then make the comment visible to moderators and Mojang only and set the security level back to public.

I am having the same issue.. my game I have been building a city in on Xbox now freezes as soon as I load it.

I created a realm and uploaded it to try it there, but it does the same.  Now I cannot get into my realm server, cannot load a dif world in there at all, or even reset a world to start a new world.

I tried reproducing the issue with a pre 1.18.30 backup of my world but so far without success. Flying into new chunks and returning to the old area doesn't seem to be the problem. I can provide a non broken version of the world too if that's of any use.

I am not sure about the loading of chunks but it sounds roughly similar. I was in my world doing some mining last night. After I ran out of pickaxes I ventured back up to my storage room to make some more at the crafting table. No longer than I step foot in the room I started getting lag spikes/freezing and eventually application closes. Now everytime I login I have the same issue with it closing or freezing and having to force close. If I login and run out of the area ASAP I can travel around a bit but I can't interact with levers/doors or anything of the sort without the game freezing/crashing. There is an ongoing ticket for it already happening on XBOX and SWITCH. I am on XBOX. 

Sounds like the same issue:

• suddenly started with bad and very unusual lag spikes

• chunks stop loading completely at some point no matter what

• can't interact with anything, all entities are frozen, can't open chests or inventory etc.

• world wont save anymore (endless saving screen)

• restarting won't fix anything, it freezes as soon as you load into the world

Just updated our Windows Server and 2 Windows Desktops (Windows 10 and Windows 11) to 1.18.30.  Both Desktops load into the game just fine, and you can look around.  But the moment you take a few steps forward the game freezes and crashes back to the desktop without any error messages displayed.

I did some more testing and after managing to get my player out of the affected area the world seems to work fine everywhere else and it saves again. I then set my simulation distance to 4 and realized it's a very specific area that causes the world to freeze. As soon as this one area gets into simulation distance it causes lag spikes and breaks the world again.

same for me , the game freezes and I am unable to break blocks and after save and quit  the process of saving is taking long and crashes resulting world to be corrupted 

Same here… only for me it’s on PlayStation. I’ve had more world for so long, the hotfix fixed it, and now it’s corrupted, says out of storage. Won’t let me load in even though I have plenty of storage. Smh. Please fix for all platforms. Including PlayStation. Bedrock has so many bugs. 

This may also be related to BDS-16839 and BDS-16847. As NeoCyania mentioned, it may be related to excessive RAM usage.

My BDS produces a core dump when it crashes that I'd be happy to share, but it's 1.5 GB when compressed. I'm not sure how to get it to the devs.

NeoCyania is really on to something. On my server, the problem only manifests when a specific user (in a specific part of the world) logs in. Users in other parts of the world are unaffected.

Just for the heck of it I tried my world last night too. It appears that the world freezes and crashes only around a certain area, which unfortunately for me happens to be homebase...LOL

Same here, for me the affected chunk is in an area with many builds near spawn that is unavoidable 😉

My world experienced this back in 1.14, but only one time – so it was not reproduceable enough to create a big report. Terrible as corruption is, I'm glad this is getting more widespread attention. 

In that situation, ONLY mobile players had issues. Their game would lock up and they would be unable to move/load in, until we killed them to move them to another area. After deleting the chunks through a world editor, the issue was resolved. 

Client side memory leak, maybe? Possibly caused by pendingticks?

Getting huge RAM usage here too, and another of my saves that was working in the new update has succumbed to this issue (MCPE-154449)

— Client side memory leak, maybe? Possibly caused by pendingticks?

Definitely not client-side, I'm seeing the issue crash the server (Bedrock Dedicated Server). Client (Minecraft for Windows) has no issues and stays responsive the entire time.

EDIT: Additionally, I can log in and log out really quick from the client, and the server still crashes after a minute of intense RAM usage.

If this helps to reproduce it somehow here are some things I did right before it corrupted:

• update world to 1.18.30

• travel to new unloaded chunks and build there for 2 hours or so

• build a nether protal to travel back to my base with lots of entities/big storage
  While I was at the storage the lag spikes started indicating some corruption happened, but the chunks where it corrupted were not loaded at that time. I later flew to that area randomly and realized the chunk freezing the world was there.

Mine will load for a moment or two once in 10 tries but I can run out the door quickly trying to get away... no dice sadly.  

Has there been any updates from the devs?

This exact thing happened to me. I opened task manager and the lag spike happens exactly when I walk into my storage room with about 50 double chests, a few shulker boxes and furnaces as well. I have 16 gigs of ram and ram usage goes from 30% to 99% when I walk into the room and while it drops to about 70% after a few seconds I cannot interact with anything or load any new chunks and I also cannot save the game as it gets stuck on the 'saving game' screen. If I close and reopen Minecraft and go back into the world I get put where the game last auto saved before the ram spike. 

I just hope the world isn't corrupted

Just to add another data point:

I had another user log in (in a non-corrupted part of the world) and, at the moment I logged in, teleport me to them. We both promptly logged out. The server crashed after a minute, but it was alive long enough to save my new location.

When I restarted the server, we were both able to log in without the server crashing. Memory usage stayed at a reasonable ~1 GB.

So, for now, that region of the world is off-limits. Hopefully we can get a fix or workaround that will heal the corruption.

On a working backup of the world the ram usage is always between 500 and 800 Mb, but on the corrupted world it's constantly using about 2 Gb. Once the world is frozen the ram usage continuously goes up.

The crashes occur on my realm at the same time the realm would have automatically created a backup, and occur whenever I do anything less mundane than villager trading or afk farming. It's painful to not be able to use a service that I am paying for.

Looks like mine got duplicated to this one.  It seems like perhaps the new render dragon can not handle too many entities in one area? On a realm I have a base that, besides the basics needed for a survival base (small farm, some animals, a couple of iron golems, building) I also have three machines.  Two for generating different wood, one for bonemeal. They are not small machines. However before the update to 1.18.30 there was absolutely no issue. Not even any lag.  But now in trying to approach that base, it crashes the game. Doesn't matter if I try to go through its nether portal or travel there normally.  Under normal travel, the first noticeable thing are mobs no longer moving, and being unable to interact with anything.  I can't even get close enough to try to dismantle the machines to see if it would help.  (Except once. That is, I got close, right in with the machines, but could do nothing about them before it crashed.  There is no corruption to see. No missing chunks etc.) The realm crashes after that, and when it is next up, I am back at the last saved point.   When someone else is on the realm and goes to that base, even though I am no where near it, the same thing happens. All mobs stop moving, can not interact with anything, and then...crash.

This has nothing to do with render dragon i think, I'm on minecraft for windows that has the render dragon engine for like 2 years now or so. I never ran into issues like this one until updating to 1.18.30. It's more likely a specific corruption issue of the world. General lag from render dragon on mobiles is a different issue.

This happened to my 2 year old survival world on a BDS (bedrock dedicated server). Similar to other users, I could log in, but would be kicked after about 10 seconds. Then I would need to manually kill the server and restart it to be able to log in again, only to be kicked again about 10 seconds later every time.

I tried many fixes including having another player travel to the same region of the world. As long as the corrupted chunks were not loaded, everything worked fine. As soon as they reached those chunks it crashed again. I also tried downloading the world. Everything worked fine offline. I then re-uploaded it with the supposedly corrupted chunks having been loaded offline, and it nevertheless continued crashing as normal.

All my fix ideas having failed, I had my BDS service roll the server back to the most recent backup, which was about 14 hours old. That fixed it — we lost the day's progress but were able to continue playing as normal. Checked the previously corrupted chunks and they were fine, no issues.

Fast forward a few hours, had been playing in a different area with no issues. Took a train that passes through the previously-but-no-longer corrupted chunks. Guess what happened? Game crashed and now the same chunks are corrupted once again. Once could have been a fluke but clearly this is a serious issue with 1.18.30. I guess my server is closed until MJ issues a fix.

Edit: forgot to mention, as other users have noted, that the memory usage spikes off the charts when the corrupted chunks are loaded.

Editing again to add more data: The corruption is in chunks that were previously loaded, not newly generated in 1.18.30. As at least one other commenter noted, it occurred for me while on a minecart rail line (in the same place traveling in a minecart both times). There are very few entities in the affected chunks — a handful of mobs and a wandering trader and some llamas. I don't believe this is related to entities. And even now, other users are able to join the server just fine as long as they don't load the corrupted chunks.

Any ideas if it's worth playing on backups or does it keep happening again and again? If the issue keeps happening it's pointless to keep playing the world cuz the progress gets lost.

@neocyania For me it happened twice, including the first time, and after restoring to backup. Both times it occurred in the same chunks. After restoring to backup, I was able to travel through the chunks at least 2 times without anything corrupting. So it's possible that it isn't guaranteed to happen again. But personally, I don't see the point in playing when it MIGHT happen. For now, I've saved multiple pre- and post-corruption versions of the world and will be waiting on MJ to issue a fix before playing again. I've let everyone on my server know that the server will be down until it's fixed.

This happened to a server I admin on, running BDS.

I loaded into the world on my local computer in singleplayer to see what the issue is,
The memory usage goes up to the max (for me 16GB) and the world struggles to load the corrupted chunks. When it eventually does load, its like the world is in a crashed state where you can't interact with anything (break or place blocks, sleep, open chests etc) in any chunks, not just the corrupted ones.  If you then try to quit the world it will get stuck on the "saving game" screen, and RAM usage will once again max out. I then forced closed Minecraft, reopened the game and tried loading into the world. It got stuck on the building terrain screen and the loading bar would not move. I tried loading into the world multiple times but could not.

When a world is corrupted this way on a BDS server, the server will not stop forcing you to have to force close it. It will also not let players join, and instead will get stuck on the "locating server" screen. Sometimes after a few forced restarts it seems players are able to join the world, but like in singpleplayer how I described earlier, you can't interact with anything (break or place blocks, sleep, open chests etc) in any chunks, not just the corrupted ones.

This is a major bug that needs fixing ASAP!

Not trying to badger or anything, but how long until I can expect this to be fixed? It's REALLY irritating.

Any ideas if it's worth playing on backups or does it keep happening again and again? If the issue keeps happening it's pointless to keep playing the world cuz the progress gets lost.

As Rogue Cheddar points out, it seems to be repeatable and related to the world data. Either something that existed before the update, or something that was changed post-update, not sure. Some of us are reporting that we played in the world for hours after updating before the problem manifested, which raises the question of whether we could load a backup and avoid doing/creating the thing that corrupted the world.

But with the number of people reporting and voting for this bug, whatever "it" is must be pretty common.

Not trying to badger or anything, but how long until I can expect this to be fixed? It's REALLY irritating.

You know as much as we do. We've had mods mark other issues as duplicates and consolidate on this issue, which is always a good sign - Thank you OcelotOnesie!

seem to be having the same issue. only in my base does it start to use all my memory then crashes. i can reload and run away from the base, reload, and then its fixed until i go near the base again. i visted many of my other areas that are thousands of block away, like my guardian farm, my crop farm, my gfs factory, gold farm, and underwater house. but only in my base does it glitch out. i unjoined the beta and went back to my old save but i had a couple hours or more progress on the beta so i hope it can get fixed. or maybe i shouldnt play seriously on beta XD

EDIT: update, its started doing the same thing on 1.18.30 as well. i cant open chests, or use pressure plates, breaking blocks yields no entities, my memory usage is 99% and the game eventually crashes. also my world loaded as an empty world with rain everywhere.

Same issue with my server. Not sure why the bds bug report was joined with this one tho.

My server is running out of memory lately... till a few days ago it used around 1-1.5Gb RAM, and now it's constantly running 2Gb with 3Gb spikes (that freeze the server since that is the ram limit), always with just 1-3 people online. The world's size is 1.5Gb.

I don’t think it’s an issue just with the beta. The new update, not even the beta, has kept me from logging into my world on Xbox because my last auto save is within two chunks of my base. It crashes out before I’m given a chance to move around. 

Yeah Mapleleafs is correct. Seems all versions of the game after the 1.18.30 update are affected. I wasn't playing on beta it was a 1.18 world and my file size was/is under 100mb. I noticed though that I can run from the affected area and save. I can interact with objects outside the effected area. Soon as I enter that chunk though lag spike then freeze. Unfortunately for me the effected area is the entrance to my branch mine there isn't even anything there. I built a set of Redstone glass doors and there is a furnace and 2 chests with a bed. Thats all. 

I'll echo all above.  I had no issues playing bedrock android pocket edition on my Realm server last night.   Woke up this morning and tried on my PC.  Got the "1.18.30 Update" notice splash screen, clicked ok, and couldn't load to realm server or even older client side saved versions of 1.18.  I think it's the 64 bit seed update.  I created a new world on Bedrock PC platform and it loads and plays fine.  All old (pre-64bit) world seed versions (client and realm) are not playable.  I also duplicated above on my Xbox One.  

Completely broke bedrock...

Pasting the description of my report here, because it’s marked as duplicate.
It contains a bug reproduction guide/demo and new information:

First occurrence: 1.18.30, reliable reproduction
When both un-rendering or re-rendering nearby areas with many detailed surfaces (lots of trapdoors, buttons, banners, plants, partial blocks etc.), internal game updates seem to freeze.

See external link for demo:
https://youtu.be/0P77bXSFvcE

Steps to Reproduce:

Notes:
It is less likely to happen the lower the render distance is set to. In my demo, I'm using a
render distance of 30 which reliably reproduces this issue for me, my recommended is 48. Render distance of 5 is preventing this from occurring

1. Load a world with many exposed/detailed surfaces, (e.g. over detailed structures) which
are causing frame rate drops, while being in close vicinity
2. Cause those said structures to become un-rendered to save resources (e.g. going below
ground while facing away from it
3. Cause them to be re-rendered, at the moment said occurs, the game stops to function
properly (-> please use video for demonstration)

Observed Results:
*Causing any progress/changes to be lost and making the world unplayable for the current session*

The game won't leave the saving screen upon closing the world.
° Inventory cannot be opened, pick block does not work
° commands (like set time) do not work
° no block updates (carpet and berry bush remain floating after removing their
supporting block)
° Entity's stop moving/lose their collision properties
° Entity's cannot be summoned into the world (e.g. by throwing a trident)
° No particles/ sound while mining blocks
° Particles work incorrectly in general (candle isn't flickering properly when lit, etc.)

I just tried it out on my world, seems like minimum render distance still crashes it no matter what. But your description seems like it makes sense! For me it mostly happens in areas with veeeery detailed builds, as soon as i get near those it lags or even crashes. In areas without those details everything feels fine. The area that 100 % crashes the world has a huge amount of trapdoors and other stuff, while areas with medium detail level only seem to cause me bad frame drops but no complete freeze or crash.

While the corrupted area in my world is also pretty heavily “detailed,” I find it strange that the server/world becomes bugged while the client remains responsive. In Luminicent Owl’s video, the player can still walk and modify the world, but the world is frozen.

Those of us running BDS are seeing the server crash, not the clients.

All this seems to point away from anything related to graphical rendering, although entity density within a chunk being loaded or updated could play a role.

The corrupted area in my world is not detailed at all. It's pretty much untouched wilderness besides the rail line going through it.

Yeah the corrupted area in my world is literally a bed, 2 chests and a furnace. Minecraft basics....

It’s Not just Windows, it’s PlayStation as well, I submitted a ticket… but no one has looked at mine, I have an 8 year old Minecraft world that now says “cannot load world” or “out of storage” this started happening after the 1.18.30 update. It loaded in once, and it was having similar issues that windows is having. Just sucks because the world is very sentimental, if I can’t play it, I just won’t play Minecraft anymore. I believe this is mainly a storage issue for large and older worlds… is there not a way to expand the storage database for worlds in Minecraft? It seems to be capped on Bedrock.. how are you supposed to keep a world and continue progressing on that world if you end up being limited because of storage. Has to be a way to fix this. I have copies of my world, just praying for one soon. Windows, PlayStation, Xbox.. anything with Bedrock Needs an update soon, hotfix maybe? 

When I enter certain chunks, my realm gets "disconnected from server." One player in my realm crashes the realm every time they join, as their character is in one of those chunks upon logging in.  I can play in certain areas on my PlayStation 4, The player that cannot log in / is crashing the realm is playing on Nintendo Switch. 

Sometimes when I log back in after being "disconnected from server" my progress is up to date, sometimes it reverts back, up to 30 minutes or so.

My realm on bedrock 1.18.30 (not playing with experimental features. 100% vanilla) 

I was returning to my main area from a creeper farm I had just built after AFK at the farm for about 2 hours I collected my gunpowder and left, as I flew back to my base I needed to sleep I landed and placed a bed on the ground slept the night, I broke my bed and flew away towards my base,  fireworks stopped working and as I was not sure what was happening as I landed I tried to set of fireworks on ground, and tried to place some blocks, nothing worked, chunks were not loading I could not go past the loaded area was like an invisible wall preventing me. Then the realm crashed sent me back to main screen,   I re loaded the realm and was back at the creeper farm I had just left, I collected my gunpowder again but the gunpowder I had previously collected was already in my invent, a little confused I flew back the same direction to my base,  my bed I placed was still in the same place on the ground yet it was still in my invent. 
I managed to recreate this duplication again with an ender chest and also shulker box full of items,   Fly away realm crash reload,  every time I re entered the realm after a crash it would place me a few seconds further forward than the last reload,   Also my firework smoke from my last flight before my realm crashed was still present on my flight path.  Day night cycle appeared to still be in motion without delay for the entire process,  I played around trying to dupe more for about 40 minutes.   I spoke to others on my realm they are having similar issues. I am windows 10, another is Xbox and switch users,   I rolled back my realm to before the issue started and again same thing happened immediately.  
Realm is unplayable…

My bedrock dedicated server appears to have an area that is experiencing world corruption. Moving around the area appears to cause the entire server to hang. The server console is still up and accepting input, but it does not respond to commands. The server will not work until it is forced to close and start up again.

Had this happen to me since yesterday after a lot of work on a new survival world.  Had a back up and loaded that today made a lot of progress for some hours then this issue happened again just now this time crashing the game completely.  before I could walk up to unloaded chunks and just stand there.  Do I delete these worlds?  I only have 2 saves left I don't even want to load them up right now because of this issue I'm in windows 10. 

I seem to have it when I quit and load a creative world and swap back and forth to try to replicate a build.     

Experienced the same thing with my MCPE-154729. Build for a few hours outside the future corrupted chunks, have a nether portal with a bunch of entities like chests near it and you got your recipe. I guess having many builds near it will also factor in.

I traveled back to my base in the nether too, just like Whitemist did. When I exited the portal in the overworld at my base the issue started (bad lag spikes). The complete freeze came on top of it when I flew to a nearby area close to spawn. The broken areas in the overworld have many builds/entities, especially my base with a big storage.

My base has taken years to build so I have to wait for this fix.  Glad to see its getting increasing attention.  Is there any way to migrate a world that has seen tons of updates over the years to properly migrate to 1.18?  The mix of chunks explored vs unexplored in my world vs new world makes a stark difference to the experience

I am experiencing this same problem in my bedrock world that I've spent hundreds of hours working on. I had exited the nether back to my base as well when my game crashed and now I can't load into the world at all

So maybe avoiding the nether for now could prevent the problem from happening? Are there any people who haven't been to the nether and their worlds were still corrupting?

I have a nether portal in the area, but I haven't been through it since updating to 1.18.30.

Noticed last night while I was playing around in my world aka fighting the freezing, I am missing the 2 stacks of Iron Ore that was in my inventory from mining before the first crash. Hopefully its still there when they fix this issue. 

This issue happened to me. It started when I was flying around moving villagers to their new trading hall when I had a large amount of lang and then it crashed. As of right now, I cant even load the world. 

Experiencing this issue on my realm as well. Realm is little over a year old on bedrock. First experienced the lag spikes in the overworld while traveling by minecart on my way to a nether portal. After I got back from the nether I experienced my first crash only after I returned to the scene of the lag spikes. Crashes occur anytime I return to that area now. I’ve tried loading previous saves, but they all seem to have the same issue in the same area. 

@neocyania my nether worked just fine, and i have portals scattered everywhere and all those locations have no issues. mine only crashes at my main base

I just add a similar video on my YouTube channel about this update 1.18.30 issue that does the same problem on my Xbox console side, easy to find me since it's on the very top of this 1.18.30 update problem in the search results on google.

Maybe the new rendering dragon engine is the cause because I can't seem to find any problems with chunks themselves when I checked them using the corrupted world files using the Universal Minecraft Editor, the chunks are normal. The entities might be the problem. Though, it needs more confirmation.

The entities on my world move fine though but I don't.

@Whitemist that doesn't sound like the same issue.

Just to summarize the comments/reports thus far, the hallmarks of this issue seem to be:

• Extremely high RAM usage (>10GB, up to consuming all physical memory on the machine)

• World/chunks stop loading

• All entities (mobs, animals, villagers, etc.) stop moving

• Blocks stop updating (e.g. break blocks below sand/sugarcane/scaffolding and nothing happens to the blocks above)

• For BDS/Realms, server crashes after several moments, disconnecting everyone

• Clients remain responsive (players can walk around, break blocks, etc.)

• All of the above triggered exclusively when a player enters a very specific part of the world.

I guess if you're playing locally (no realm/server) the RAM explosion could start affecting your performance/FPS, but that's just an unfortunate coincidence.

We keep using the term "corruption" not because anyone has confirmed our world files have in fact become corrupted, but because the issue is triggered by loading some thing in a specific part of our worlds. We've taken a lot of guesses about what that thing is (Nether portals, traveling to/from nether, lots of storage/chests, lots of entities, etc.) but for every guess we make there seems to be a counterexample, so we really don't know.

We're experiencing the same in our realm, and have a general area we know the freeze/crash will occur in. I used amulet map editor, and tried to narrow down which specific chunks were causing the issue, but no amount of chunk deleting helped – I literally deleted all chunks in the world, and the issue persisted. Strangely, some of the mobs were still present even though I'd deleted all the chunks, and that's when I realized that amulet doesn't remove entity data... and that's almost certainly what's causing this (at least in my case).

I'd upload a copy of my world, but even with just the entity data, the size is ~48MB (I know), which is too big for the bug tracker.

I think if you can narrow down the affected chunks, and delete all entity data therein, you might have a fix. I'll be trying this later if I can find an appropriate tool for editing Bedrock entity data. If it works, it'll be great, but I sure will feel bad for my friend's trading hall that's right at the middle of this corrupted area.

Edit: Apparently media fire links are allowed.

https://www.mediafire.com/file/q564owyntz222oc/Creeper_Craft_-_No_Chunks.mcworld/file

Once loaded, just walk toward -300, -200, look for the falling villagers, and eventually the game will freeze as described by other comments here.

I'm experiencing the same issues since 1.18.30 with bedrock server world (windows 11).  I had raised a separate (duplicate) issue but will add here for completeness... 

Note: This world was started in 1.18.2.03 (28 Jan 2022) and it has become quite active with 4-7 players daily.  

Gameplay experience after 1.18.30

• for the first day or so, the world was working fine with multiple players

• after a while, minecart travel stopped working.  during travel, the player stopped moving, cart dissappeared.  it was found at the end of the track

• apart from the cart glitch, it seemed pretty normal.  The affected user found the cart could not be picked up though even after they did "Save and Quit" which usually solves small consistency issues

Things started going downhill

• the server started to lock up and needed restarting

• users found that the world did nothing

• users tried to disconnect from their client but the server did not report that they had disconnected.  It seemed like it wasn't responding so it was restarted. 

• upon restart, all sorts of weirdness.  could not interact with blocks

Memory issues started

• several restarts later...

• the server is crashing now, due to out of memory 

• memory peaks at 24GB+ allocated to bedrock_server.exe

• the memory issues now occur as soon as anyone enters the world (doesn't matter who).  It climbs very quickly to 20GB+ and bounces up and down a little and then crashes

When it happened to me a few days ago on a week old world I thought it was related to a hardcore mode addon I installed.  I deleted it, restarted my world on the same seed and rebuilt things to where I had them in creative then started finishing my starter base.  It saved multiple times that day, no issues at all I played built my base gathered resourced locally, dug down to diamond level under my build.  No issue until I checked something in my creative world came back to move some lanterns and immediately noticed the lag and ram spike and then my world crashed.   My world never crashed on the original problem it just didn't load certain areas around my base.  In this new version I haven't ever loaded those chunks.  I just teleported the 14,000 blocks to where I decided to build my stuff. 

I loaded 1 of my 4 backups that I just created after my previous save and it pretty much crashed before it built the world.   The files that crashed are all around 16MB now but the 1 world I haven't loaded back up yet is at 65MB if that gives any clues.  Both times quitting and going to a creative world quickly quitting again and coming back to my survival world caused this issue for me.  If uploading any of this data could help point me in that direction I don't really know what I'm doing.    I'm on the windows 10 version.    I appreciate reading everyone's updates and thoughts on this. 

I've got the exact same issue.

When 1.18.30 came out, the game updated completely fine (I'm on Xbox btw) and i loaded in completely fine. This is on one of my friends realms. A few days ago, i could load in but, half of the map loaded in and i could only turn in one spot. A couple of times i was able to move around. After about 5 seconds or so, i get "Disconnected from Server". 

I WANT TO PLAY IT AGAIN!!!!! I was doing so well in the Realm. I was getting lots of loot and diamonds and i just made a storage room.

I hope Mojang fix this issue.

Also having the same issue on my realm

Started maybe a day or two after the most recent update, it started in one area and everytime anyone went there it would cause severe lag mobs stop moving/disappear, you can't interact with doors, chests ect and breaking and placing blocks would be super laggy, and eventually everyone who was on the realm would get disconnected and not be able to join back for quite some time, it then stopped for a day or two and we thought everything was fine however it has now started in a completely different area doing the exact same thing.

For clarification all the other people in the realm and I are just playing the game as normal.

Hello,

I managed to run strace with my bedrock server and it seems that its stuck with nanosleep with 100% CPU usage eating more RAM then it crashes

mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f3e333fd000
mprotect(0x7f3e333fe000, 8388608, PROT_READ|PROT_WRITE) = 0
clone(child_stack=0x7f3e33bfcd70, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE                                                                                                                                                                                            _PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x7f3e33bfd9d0, tls=0x7f3e33bfd700, child_tidptr=0x7f3e33bfd9d0) = 23939
write(1, "[2022-04-26 10:50:02:539 INFO] S"..., 47) = 47
nanosleep({tv_sec=0, tv_nsec=49986596}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49979576}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49978578}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49976230}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49975400}, 0x7ffc36d0d470) = 0
[cut 1458 lines]
nanosleep({tv_sec=0, tv_nsec=49979189}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49983575}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49979432}, 0x7ffc36d0d470) = 0
nanosleep({tv_sec=0, tv_nsec=49954216},  <unfinished ...>) = ?
+++ exited with 1 +++

My platform is an iPad.  Upgrade to 1.18.30 completed successfully a few days ago.  Yesterday, I attempted to load my world and the app crashed about 3/4 during the loading progress bar.  Attempted this several times.  No happiness… except once.  One time the App completed loading, but most blocks were transparent (like x-ray mode) and the game crashed within a few seconds.

@Michal Brzek Awesome job using strace! BDS often has multiple threads doing things, so it's not surprising that some of them are sleeping while others are busy/crashing. If you run strace with all the bedrock server threads, you'll see more activity, but none of it sticks out as unusual to me. lseek() and read() calls for reading world data from disk, sendto() and recvfrom() for network traffic between client/server, and plenty of nanosleeps while threads wait on things. If I have time, I'll try to compare strace logs between a healthy server and a crashing one to see if anything sticks out.

If you want to dig a bit further, when BDS crashes, it generates a huge file called "core", which is a core dump. You can try to read it with gdb with `gdb ./bedrock_server-1.18.30.04 ./core`. You can see the state of all threads running with `thread apply all bt`. You'll see a lot of `??` because we don't have the debug symbols (names for anything "inside" Minecraft), but you can usually see what system calls the program was in at the time of the crash.

Unfortunately, that's still not super helpful (at least not without the debug symbols mentioned above). The BDS seems busy doing something while consuming all the memory on the system, until the OS OOM killer finally kills it for hogging all the memory. So the BDS isn't hitting a wall, it's stuck in a loop. But I usually see the main thread doing something involving memcmp or memmove when it crashes - indicating that it's probably stuck loading more and more of something into memory.

I have looked at two affected worlds, and they showed different memory usage in task manager.

The first world was unmodified by external editors. I checked Task Manager during the memory spike and it showed that the excess RAM usage was not allocated directly to Minecraft, but was instead being used to cache data waiting to be written to disk.

Then I checked tried the world with chunk data removed by Amulet, and Task Manager showed RAM usage by Minecraft jumping to about 2.5 GB and system memory maxing out for a few seconds but then coming back down, with a negligible amount cached for writing to disk. The world never crashed completely but it appeared that the server-side thread crashed--I was able to fly around but entities were frozen, blocks did not have breaking particles, and when I tried to Save & Quit the saving process hung for many minutes until I force-closed the game.

It seems that the way entities are stored in the world save has changed in 1.18.30 (programs that can show chunk data for chunks generated prior to 1.16.100 no longer find any entities in chunks after the world is opened and saved in 1.18.30). Based on that and chunk deletion not clearing the crash it seems the problem has to do with converting entity data to the new format in pre-existing chunks.

Another observation from a casual player (I commented earlier as well), I decided to test creating a new 2 player Realm.  Before I did, I created a client side (non-realm) world on my PC.  It played fine with no issues for several hours today.  I then downloaded a copy.  After that, I created a brand new 2 player Realm and uploaded that world to that new Realm.  It played fine for about 30 mins, no issues.  I then decided to try uploading my "corrupt" world from my 10 player realm (pre-1.18.30 update creation)  to this new 'test' 2 player realm and as soon as I loaded it and logged in, same issues as I experienced on the 10 player realm.    I couldn't open chest, inventory, interact with blocks, etc.  All as previously mentioned above by myself and others.  I then 'x' out of the game without saving and restarted, except now the 2 player realm is unreachable or I can't log into now, just as my corrupted 10 player realm.  

So...  It appears to me that  [MOD]GoldenHelment might be on to something with the following comment..

 [{*}MOD]GoldenHelment{*} :   "....It seems that the way entities are stored in the world save has changed in 1.18.30 (programs that can show chunk data for chunks generated prior to 1.16.100 no longer find any entities in chunks after the world is opened and saved in 1.18.30). Based on that and chunk deletion not clearing the crash it seems the problem has to do with converting entity data to the new format in pre-existing chunks."

[MOD]GoldenHelmet might be right on the spot. I can confirm the chunks I have most trouble with are old chunks with 125 entities, more less with other chunks being that range too.

I can confirm:

That are deleting chunks doesn't fix the problem.

Prior chunks to 1.16.1 had problems, but new ones don't.

If you manage to save and quit, the worldfile has it's file size, keep increasing.

The save and quit saving process hangs for minutes unless you just force close.

Though, weirdly enough, in some old chunks, I can open chests, entities moves, break blocks and other actions, and in others, it's the opposite.

So I thought I'd try and download a backup and see if it lags/glitches when playing offline however it kept on getting stuck at 654MB I checked my internet speed and that was fine, I also tried it the next day and it got stuck again at 654MB.

I then looked into the file sizes for all the recent back ups and the size is around the same size for the most part (roughly 1700MB) but when someone has entered the lag/glitch chunk the file size jumps up in size (around 1900-2000MB) 

Not sure if this is helpful.

Whitemist said "Prior chunks to 1.16.1 had problems, but new ones don't."  But my problem that seems to match this is from being built in 1.18.12. Not all that long before the patch to 1.18.30.

Yea this issue has also happened to my world! And i cant even play now Xbox 1. Sometimes trying to log in to the world my game crashes and sometimes its instant or a few secs after but my game crash no longer then 10 secs loading the world will crash. Getting sick of theses bugs!

Just to confirm the impact of this.  

I can easily rollback Bedrock Server to a prior version 1.18.30 

However, clients on iOS will not be able to connect to the Bedrock Server since it enforces version parity.  iOS clients are essentially stuck on 1.18.30

So, in our case it's essentially bricked at the moment, unless we begin a new world from scratch in 1.18.30, which is very undesirable.  

It stands to reason that we all hope that workarounds will be considered soon if solutions are not imminent.  

If you need, I'm happy to provide world files from our bedrock server (backups immediately prior to 1.18.30 and other backups after things go bad).  

Or I can do testing on a beta when you're ready with that.  Whatever helps.  

The devs are appreciated nonetheless, they have built a great game that we all love

Just a heads up to anyone following this thread they just pushed 1.18.31 out that addresses this bug plus a few others.  I loaded up my world and played around a bit and it does seem to have been solved at least for me.  Thank you Devs appreciate your hard work.

The update to 1.18.31 fixed the crash during loading issue on my iPad.  It also dropped the save file size from 105 to 98MB.  As above, thank you Devs and those who contributed debug reports to getting this issue quickly resolved.  It is appreciated.

Chiming in to confirm, 1.18.31 fixed the issue on my BDS.

I re-entered the area with the "bad" chunk, and at first there were no entities, and some chunks wouldn't load. But the server RAM usage stayed steady. Fearing for the worst, I opened a door and voila! Everything started working again. Villagers, animals, mobs, missing chunks, everything came back. I played for 30 minutes in the same area and had zero problems.

So if you load up your world again in 1.18.31 and find a creepy ghost town, just interact with something (door, bed, maybe break a block) to bring everyone back Avengers Endgame style.

Thank you to the devs for their quick work!

The new update 1.18.31 works.  Mine was a bit laggy at first due to how many entities I had per chunk but it worked. It slowly stabilized

It is all fixed and also the save file decreased from 390+ MB to 379 MB.

The devs really fixed it fast.

Edit: I also tried multiple world copies of my previous attempts at trying to fix the chunks (10 copies) and it all worked fine

As of the new update, 1.18.31, my world is still corrupted and experiencing the same issue, I’m on PlayStation Bedrock, I have backups.. they aren’t working as well. Am I able to submit a private ticket so the mods can look into my world? I’m devastated I have had this world for 8 years.. coming on 9, it’s very sentimental. 

it loaded in once and had all those pink and black blocks.. I believe my file size is just too large, is there a way to downsize unnecessary chunks in my world that don’t have builds? Areas that have only been explored to downsize the file.. I don’t know what to do. This all started happening after 1.18.30. Can I submit a private ticket with a world save attached to it? 

Looks like 1.18.31 fixed the world for me and everything works fine again, thanks for the quick fix!

Thank you so much Mojang team! It really works now with this new update!

1.18.31 fixed it!

@unknown: We're going to track your issue at MCPE-154121. If you can, please do provide a copy of the affected world.

So I saw the update yesterday when I got home from work and I was super hopeful. But alas no dice. My world is still corrupted and still behaves/acts in the same manner prior to the patch. 

This is still not fixed for the switch.  We do not have option to download 1.18.31.  All tickets including MCPE-154110 are closed and should not be.

I have opened MCPE-154950 to ensure we have tracking for when 1.18.31 is available for Nintendo Switch.

1.18.31 looking good, thank you!

There is still the "memory not unloading" issue. The update did prevent the server from crashing (now RAM doesn't grow without limits till it crash the game and computer possibly). But the loaded memory doesn't free up after a player leaves: which results once again in server freeze, only after a longer period of time (and depending on the number of players who joined ig).

OcelotOnesie, I have submitted a private ticket for MCPE-154121 attaching my file in the comment, shared to One Drive. 

thank you to the dev team for taking the time to find the issues and to finding a fix, it is greatly appreciated, please let me know if there is anything else you need. 

So I tried my world and now its worse. It actually won't get past "building terrain" before it crashes. =(

It still is freezing on my switch during autosaves. 

Downloaded the new update and it works ! Mojang fixed whatever was wrong with my old world. Been playing in it over an hour now....

Yes, mine was marked as resolved in one of the linked cases. This is definitely not resolved in 1.18.31 BDS-16889. Same issue still occurring

downloaded the new update still not working on new bedrock server, CPU at max, RAM at max chunks not loading.

I haven't been playing because of the issue, now that it shows resolved I'm getting back in and now NONE of my worlds work for more than a couple of minutes before Minecraft crashes.  (update) So I started a new world since old worlds still don't work. My new world is now having the same issue, and I wanted to add maybe this little tid-bit... I've noticed that just before my old world crashed and this world started crashing there was a problem with rain... It wouldn't stop after sleeping. It took a couple of in-game days before the game crashed after the rain issue began, but it seems to be a precursor issue (you can resolve it by logging out and back in, which shows the day as it should be... sunny).

@BedwokServer
Its probably because of server lag.

@wan6845

its a local server, but anyway its fixed now that I pulled a backup of a week ago, just lost a few days of progress no biggie 😞

I didn`t have time and I wasn't checking but today I can confirm that at 1.18.32.02 everything is working properly. Thank You

I'm on 1.18.32 android, opened my save and travelled to my city with lots of villagers, chests, animals, beacons etc. Suddenly there's a big lag spike, which eventually crashed and closed the game. I tried to open my Minecraft save again, and spawned in my city, which again froze & crashed the game (and this time it crashed the phone itself, forcing it to restart). The third time I opened Minecraft, I noticed that the GUI is larger for some reason. I tried to open that save again, and miraculously it worked without lag spikes or crashes. It doesn't seem like there's data corruption so far. Restarting the app fixed the GUI.

It seems like 1.18.32 has fixed this bug partially but not completely. The lag spikes and freezing can still happen, but fortunately it doesn't lead to world corruption, at least for me. Worlds with larger file sizes seem to crash more often, especially if it gets to the gigabytes. Personally I dislike non-renewable resources like Allays, dead bush etc because it forces you to explore new terrain and increase the file size further. Anyway, thank you devs for all the hard work, world corruption glitches are the worst.

Not sure why this says it's resolved. In whatever iteration of 1.19 is most recent and the autosave lag is awful. Wouldn't be so bad if it just autosaved every once in a while, but it literally saves every time i take off with my elytra, and takes ages to finish. if i land, i have to wait 30+ seconds for the auto save icon to go away before i can take off again. 

Issue not fixed. Duplicated in MCPE-155469