[Crash] Exception ticking world entities, dirty controller no registered controllers etc.
Bjonnfesk opened this issue ยท 4 comments
https://gist.github.com/Bjonnfesk/96dc4d9f58d187672becbd52987ce55e
In short, #1132 #1514 #1828 is back to haunt us.
I am now sometimes unable to start my server, as this exception occurs on the very first tick and locks the thread until the Server Watchdog kills the server. We have a single Alveary with many Frame Holders from Career Bees, all with Proven Frames. I will assist in any way I can to find out what happens here; while I haven't written any Minecraft mods, I have experience with Java and programming in general.
It is worth noting that the server is currently running on an underpowered VPS due to technical difficulties with my usual dedicated server, so it does have some tick lag issues.
I will try updating that Java version, without really having much hope that it will help, then variously:
- Removing CareerBees (re-adding it after loading the world without it, if possible)
- Restoring from backup
- Removing CareerBees and Forestry (re-adding them after loading the world without them, if possible)
- Deleting the chunk with the Alveary in it
Edit: I now have the server running again, and it seems to be working just fine including the Alveary.
Any other suggestions?
I took the liberty of examining the function in question, addDirtyController() of MultiblockRegistry.java. I noted that the Javadoc asserts the following:
Call to mark a controller as dirty. Dirty means that parts have been added or removed this tick.
No parts were added to or removed from any multiblock structure, Forestry or otherwise, for at least half an hour before the first crash occured.
Happened again.
https://pastebin.com/fncGFgar
This time while the only player online was AFK staring at an OpenComputers screen, and no Forestry, Binnie's, Gendustry etc. stuff was going on. All Forestry-related machines, apiaries and so on were simply idling, untouched for days.
Relevant part of latest.log:
https://pastebin.com/SHK7YLq3
On restart, the server spat an error about failing to save files ("Did the server never start?") from OpenComputers, but otherwise seems fine. Note that the crash report says no players were online, that's only because I was kicked with a "Server closed" message (as is evident from latest.log), I was online (AFK) when the crash actually happened.
I should mention that the ticklag has now largely been solved as a result of removing troublesome Railcraft tanks, possibly related to Nuclearcraft#633.
