Concurrent Chunk Management Engine

Concurrent Chunk Management Engine

2M Downloads

Crash on world save in 1.21.6

vladkrv opened this issue ยท 4 comments

commented

Describe the bug
When exiting a game and saving the world you stuck indefinitely in the "Saving world" state. When looking into logs, I see that game actually crashed.

To Reproduce
Steps to reproduce the behavior:

  1. Create a and load the world
  2. Do something (run for a second)
  3. Save and exit
  4. It's stuck, with the last log being "[16:33:32] [Server thread/INFO]: left the game"

Expected behavior
Game saves properly

Screenshots
None are needed

Runtime info (please complete the following information):

  • OS: W11 24H2
  • Minecraft version: 1.21.6
  • Mod version: c2me-fabric-mc1.21.6-0.3.4+alpha.0.42

Crash reports / logs
Link: https://pastebin.com/tXYA3ZKW (valid for 2 weeks)
Pass: PyJExjaCrh

Other mods
None

Checklist

  • I am using the official version of the mod.
  • I tried the latest development version but the issue persists.
  • I searched for similar open issues and could not find an existing bug report on this. (there are many similar bugs but I couldn't find exactly this case)

Additional context
I'm using prism launcher, if that matters.

commented

Good point. I'll change that in advance. Other than that, I've tried a couple of different scenarios, and as long as the host instance is launched in online mode, everything works fine. I'll close the ticket and will get back if I find more details.

Again, I highly appreciate your quick support. Have a great day.

commented

Cannot reproduce. Try reproduce without C2ME.
Please try reinstalling your launcher and the instance, and launch in online mode.

commented

Launching in online mode seems to resolve the issue. Is there any reason it works that way? It would be great to note it somewhere.

Also thank you for such a prompt response.

commented

Launching in online mode seems to resolve the issue. Is there any reason it works that way? It would be great to note it somewhere.

Launching in offline mode works for me for some reason. I also have no clue what exactly is going on. My best guess is that the commas and spaces in the instance directory name can probably affect things.