Leaving and joining a save throws exceptions and causes the game to freeze
Closed this issue · 1 comments
Version: 0.5.4g
Log:
latest.log
Opened Test World 1. Moved into new chunks. Satisfied new map chunks were loading, I saved and quit. Then, without closing Minecraft, I opened Test World 2. That loaded fine. I then saved and quit that world. However, Minecraft then wouldn't move past the "Saving world" screen. Had to use Task Manager to close Minecraft as not even alt-F4 could kill it.
In the log from the second world, the following log line appeared, which I would assume is related:
[16:43:42] [Blaze Map (Client) Debouncer Thread/ERROR]: Exception in DebouncingThread main loop!
No further detail or stack trace accompanied that error line.
However, on closing Test World 1, each of the Render threads did throw an error and crash, as is expected when the main game thread closes. My suspicion is that these killed threads might have caused issues when reloading the other world, causing the error in the DebouncingThread and not allowing the world to save and quit properly.
Replicating going the other way (loading Test World 2 first, moving into new chunks, save and quitting while chunks still loading, then opening Test World 1) also showed the DebouncingThread error, except the game also hung on loading, which I'm not sure if that's specifically related to this issue or if that's more related to #12 , since it was closed while still generating chunks.
Log from replication
latest.log
First issue: Better logging for the exception from DebouncingThread to see what it's being caused by. Then can figure out how to fix it