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
Rare crash bug #835
Comments
This certainly has something to do with @aikar's timings, but I'm not sure exactly what's triggering it. It would probably be worthwhile for him to look at this issue though. |
The issue is not with timings, but in that something is trying to add to Timings async |
So yeah, timings only really make sense from the main thread. Why do we have anything but startTimingIfSync and stopTimingIfSync -- what is the use in allowing folks to start timings from other threads? |
For when you don't know (Plugins) |
This is not caused by an async timing call. You can see it's in the tick method |
That would imply something is causing a chunk to load async. One thing I did in paper is that if this ever happens, to force it sync: |
This has happened a few more times, and I think it's somehow related to chunk loaders. |
Since updating SpongeForge, this has not happened in three days now when it used to happen about 3 times per day. |
Looks like it's happening again. Nevermind. It's still a valid bug. |
I've went hours upon hours of chunk loading and cannot reproduce this. |
This has happened once, not sure if it's a very serious issue but it seems to be incredibly rare.
The server randomly stopped with "Server Closed." as usual "Exception in server tick loop" crashes do.
I'm not 100% sure who is at fault here, but I figure that it's a problem that can be fixed in SpongeCommon because I believe that SpongeCommon is where the co.aikar.timings is implemented (?).
I figure this is a good place to start at the very least.
This is probably just an issue with aikar, and if it is please let me know and I will close this and contact aikar about it.
The text was updated successfully, but these errors were encountered: