Bedrock Server Crashes after 10 minutes, 5 players, 24GB memory.
As soon as any single player joins, the memory climbs by Gigabytes until the machine and the machine hits 99%, then drops down and quickly climbs again. Eventually the application crashes.
Eventually, the server crashes after a short time (within 5-10 minutes usually, sometimes longer).
The server has become less-and-less responsive and I wonder whether our world is becoming corrupt or something, since it appears to be far less stable than a day ago.
Is there are new beta I can try? This latest 1.18.30 release is unplayable
[media]
Related issues
Attachments
Comments
migrated
migrated
Please let me know if there's any more information you need. I can provide the world file if you want to take a look at that.
We didn't have any issues at all with this world until 1.18 but now it is unusuable. I suspect there is a bug that this world is able to reproduce, so it may be worth taking a look
Thanks
migrated
Sometimes the crash is reported in Windows Event Viewer.
Faulting application name: bedrock_server.exe, version: 0.0.0.0, time stamp: 0x624cf184
Faulting module name: ucrtbase.dll, version: 10.0.22000.1, time stamp: 0x00e78ce9
Exception code: 0xc0000409
Fault offset: 0x000000000007c648
Faulting process ID: 0x718
Faulting application start time: 0x01d856178fd240d8
Faulting application path: C:\Users\deang\Minecraft\bedrock-server-1.18.30.04\bedrock_server.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: a018c101-eeaf-402d-bda1-d0ec2eab8c29
Faulting package full name:
Faulting package-relative application ID:
Vincent294
Seeing 100% CPU on 1 core and a lot of RAM allocated on my Ubuntu 20.04 server. Server unresponsive, it worked with 1.18.30 for the first day. I'm gonna back up my corrupted save and restore a backup in the meantime.
Edit: 0xc0000409 is the Windows hex error for stack overflow if I recall. Probably infinite loop putting something on the stack.
[Mod] OcelotOnesie
We're tracking this issue at MCPE-154278, so I will resolve and link this ticket as a duplicate.