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

Random crash. Not sure related #1

Closed
Punkred opened this issue Jan 25, 2016 · 3 comments
Closed

Random crash. Not sure related #1

Punkred opened this issue Jan 25, 2016 · 3 comments
Labels
plugin Issue cause relates to a plugin.

Comments

@Punkred
Copy link

Punkred commented Jan 25, 2016

Server randomly hangs after several hours of uptime. I noticed tps randomly dipped to 9 then went back up to 20 before this happened. Heres the only error i see other than one for a deathevent from mobstacker that happened once. http://pastebin.com/raw/CLPgscC8 It says to report to paperspigot so maybe you can guide me in the right direction.

@Techcable
Copy link
Contributor

Deadlock with enjin.
This is their issue.

@Punkred
Copy link
Author

Punkred commented Jan 25, 2016

Holy crap dude thanks for letting me know this has been bugging me for awhile

@Techcable
Copy link
Contributor

Yup, no problem.
@Zbob750 please close

@zachbr zachbr closed this as completed Jan 26, 2016
@Executioner1376 Executioner1376 mentioned this issue Mar 11, 2017
@Xayanix Xayanix mentioned this issue May 29, 2017
@lopoo lopoo mentioned this issue Jun 20, 2018
Trigary added a commit to Trigary/Paper that referenced this issue Sep 15, 2018
@Unknownio Unknownio mentioned this issue May 2, 2021
3 tasks
nothub referenced this issue in nothub/paper-1.12.2 May 24, 2021
For some unknown reason, Minecraft is sleeping 10ms between every single chunk being saved to disk.
Under high chunk load/unload activity (lots of movement / teleporting), this causes the chunk unload queue
to build up in size.

This has multiple impacts:
1) Performance of the unload queue itself - The save thread is pretty ineffecient for how it accesses it
   By letting the queue get larger, checking and popping work off the queue can get less performant.
2) Performance of chunk loading - As with #1, chunk loads also have to check this queue when loading
   chunk data so that it doesn't load stale data if new data is pending write to disk.
3) Memory Usage - The entire chunk has been serialized to NBT, and now sits in this queue. This leads to
   elevated memory usage, and then the objects used in the serialization sit around longer than needed,
   resulting in promotion to Old Generation instead of dying young.

If there is work to do, then the thread should be doing its work, and only sleep when it is done.
amit177 pushed a commit to amit177/Paper that referenced this issue Dec 11, 2021
@ghost ghost mentioned this issue Oct 13, 2022
pajama10000 added a commit to CanadaMC/CanadaMC that referenced this issue Nov 1, 2022
DavidTs93 added a commit to DavidTs93/Paper that referenced this issue Apr 7, 2023
kennytv pushed a commit to DavidTs93/Paper that referenced this issue Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
plugin Issue cause relates to a plugin.
Projects
None yet
Development

No branches or pull requests

4 participants