Server crashes constantly

BDS's World Corruption problem is linked to the storage issue of the bedrock edition.
(https://bugs.mojang.com/browse/MCPE-32501)

If the Storage issue is fixed, it is estimated that BDS's World Corruption problem will also be resolved.

Hi Anatoly,

Are you able to provide more information about your setup. IE is the world size large etc? I don't see these crashes on any of my servers so just trying to get as much information about this issue as I can.

Ionic

@IonicEcho it's 2.6 Gb world. What setup do you want me to provide? It's just world been migrating through several MC version

This happen even if you do a "stop" command

What OS are you running on?

Ubuntu 18 BDS

The same happens with Windows 10 based (Windows Server 2016).

Awesome thank you so much for testing that.

If you're able to zip the world files and upload them I'd be keen to take a look. Otherwise BDS automatically logs crashes with Mojang so they should have what they need to investigate.

I guess I'm asking more out of curiosity to see if we can fix it for you if its world specific.

Edit: 1.14.30 came out last night too, if you can try that I can update the affected versions if its still occurring

It is still happening 

I think this problem has something to do with the Storage issue of the Bedrock edition.
https://bugs.mojang.com/browse/MCPE-32501
Please refer to the above report.

Thanks Otocin,

I don't think we have any evidence to relate the two, will ask around though. Have updated the affected versions for you too.

The two have something in common.
The first is that it was caused by a 1.13 Buzzy bees patch.
The second is that the corruption occurs when a lot of chunks are loaded.

Experiments have shown that when playing single(local) and BDS using a single world ,
a collision has occurred in the same situation(when loading many chunks).

I play on a server that crashes very often. The server admin says that the timed routine that handles backups calls the save hold operation and this can sometimes cause the system to become unresponsive and finally crash. For us players this shows as the game freezing so that you can't interact with blocks and then disconnecting us. After relogin there is a 1-2 minute rollback. The worst part is that the player inventory seems to get saved for a bit longer than the chunk information. That means there is a risk that any items placed or removed from player inventory in the wrong time will disappear from the game completely. One of our players lost a shulker containing loot from several hours of exploring this way.

I'm getting the same problem, only when using worlds over 1GB, so I do believe it's the same issue as the general Bedrock storage problem that's been going on for 2 years.  Just tried it with a 4.6GB world and got the same crash. I don't get crashes like this with worlds under 1GB.  This isn't only a BDS problem.  The same worlds that crash BDS also crash single player Bedrock as Otocin mentioned.  The only difference is BDS seems to hold on a few seconds longer before crashing.

(First time using this site, sorry for some noobishness on the pictures)

Client side (Android):

Hi all,

Would anyone thats able to reliably reproduce this be able to give 1.14.32.1 a go that was released last night.

I know no more than you do but its possible the fixes that went in for realms last week have been included in the new release last night.

Thanks!
Ionic

Perfect! There is no more wold corruption! Thanks you!

it seems to be fixed now thanks you very much! I will edit this comment if it starts happening again!

We are still having this issue after upgrading to 1.14.32.1.  We usually see block lag first and then the server restarts.  If members try to log in too quick after the restart, they will get the dialog about world corruption.  I have not been able to find a pattern with particular users or activities on the server.  What information should I provide to help resolve this?

Please reopen this issue.  When the server crashes we have members that are losing items or items are being duplicated.  I have not been able to find a pattern as to what leads to either outcome.

Hi Sentre,

All crashes are logged automatically to Mojang. Its impossible to track random crashes so its really not helpful for us to keep a ticket open for it here. We'd have no way to truely know if it was resolved.

The crashing related to large world sizes (the cause of this ticket) was quantifiable so worth tracking as it was possible to reproduce (just needed a large world).

If you know exactly how to repro your crash please feel free to create a new report, including detail on your environment and how to repro the crash. However if its just a random crash we need to leave it to Mojangs internal processes.

Ionic

Thx Ionic.  Our world is abt 1.2GB.  I'll see if I can trim it for now and if I can figure out a pattern I'll open another bug.