mojira.dev
MC-149215

Game deadlock after quitting world in a chunk that does not exist

When flying out, one can get to a state where no chunks are being rendered, and the player is permanently "waiting for chunk". The game will never send the client a single chunk, and if the player quits the game in this state, the game gets stuck on "saving world" screen permanently, while eating up more and more memory (suggests a memory leak).

Related issues

Comments

migrated

Just happened to me. Same circumstances. I was flying with elytra and entering newly generated areas, new chunks eventually stopped loading. Hoping exiting and reloading would fix it, I tried to save and exit. Game is still stuck on "Saving World" screen as I type this.

marcono1234

Are you still experiencing this in the latest version (currently 20w13b)?
And does saving the world finish when you wait a little bit longer (e.g. 30 seconds or more)?

I cannot reproduce this currently.

migrated

This happened to me on Linux Mint 20.1 (not via VM). My CPU is an AMD Ryzen 5 3400G with integrated Vega 11 graphics. On modded Minecraft, version 1.16.5, I used the /locatebiome command to locate a specific biome in the Nether and then teleported to it. The chunks stopped loading after awhile and the chunks to my Nether portal had unloaded and wouldn't load. After 15 minutes or so, I proceeded to press Save and Quit, hoping that this would solve the problem, but it became stuck at the "Saving World" screen. Even 50 minutes later, it still hadn't saved my game. Initially, I thought that this might be Optifine's fault, but I found this page and realised thay my case perfectly matches this bug.

marcono1234

On modded Minecraft

Please note that in general we do not accept reports about modded installations here because the mods might be causing the bug. Please test whether this also occurs with an unmodded installation.

migrated

(Unassigned)

Unconfirmed

Chunk loading

Minecraft 1.14

Retrieved