Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server segfault #1742

Closed
5HT2 opened this issue Feb 24, 2022 · 3 comments
Closed

Server segfault #1742

5HT2 opened this issue Feb 24, 2022 · 3 comments
Labels
status: resolved Job's done!

Comments

@5HT2
Copy link

5HT2 commented Feb 24, 2022

Game Version: 1.16.3
Platform: Windows / Mac / Linux (which?)
Modded: No / Yes (which?)

Auto_Map_Markers.zip
CarryCapacity-VS1.16.0-v0.6.4.zip
FarmlandDropsSoil-VS1.15-v1.4.0.zip

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

@5HT2 5HT2 added the status: new This issue is fresh! label Feb 24, 2022
@5HT2
Copy link
Author

5HT2 commented Feb 24, 2022

After poking around a bit, I found mono/mono#12947.

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 5HT2 changed the title Server segfault after player killed a bell Server segfault Feb 24, 2022
@tyronx
Copy link
Contributor

tyronx commented 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

@tyronx tyronx closed this as completed Feb 24, 2022
@5HT2
Copy link
Author

5HT2 commented Feb 24, 2022

Thank you, I'll update this issue if it happens again.

@copygirl copygirl added status: resolved Job's done! and removed status: new This issue is fresh! labels Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: resolved Job's done!
Projects
None yet
Development

No branches or pull requests

3 participants