You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is in-line with what I was experiencing, after going through several translocators, where loading new chunks slowed to a crawl (30 to 60 seconds each time).
My server is on a 10 gbit connection with 24GB of ram and 4 cores, and cpu usage was around 40% during the chunk loading.
Also, to test, attempting to teleport with the command within the same chunk (no more than 5 blocks in front of you) still had a 50 second delay before it worked, while other actions didn't have such latency.
5HT2
changed the title
Server segfault after player killed a bell
Server segfault
Feb 24, 2022
Sounds like you are hitting a memory soft-limit. Please run this command and reopen the ticket if it still happens after that: sudo sysctl -w vm.max_map_count=262144
Game Version: 1.16.3
Platform: Windows / Mac / Linux (which?)
Modded: No / Yes (which?)
SP/MP: Singleplayer / Multiplayer (which?)
Description
Explain the issue you're running into.
Server segfault after player killed a bell. I don't think this is related to killing the bell, it just looks like a fluke with the autosaving.
Logs: https://cdn.l1v.in/paste-16456844301.txt
The text was updated successfully, but these errors were encountered: