Saving and exiting a world in Minecraft 1.21.1 (unmodded/vanilla) will freeze the game, it feels like the exit-world mechanism has a deadlock as it won't stop showing "Saving world" in the game.
Temporary Workaround: Kill the process to restart Minecraft.
Yes, the world seems to be properly saved when killing the process although the game still shows "Saving world"
Yes, the minecraft client is unmodded/unmodified.
Attachments
Comments 8
I've attached a recording. The game won't exit from the world as described above.
No suspicious console output:
[16:37:34] [Render thread/INFO]: Loaded 1290 recipes
[16:37:34] [Render thread/INFO]: Loaded 1399 advancements
[16:37:34] [Server thread/INFO]: Starting integrated minecraft server version 1.21.1
[16:37:34] [Server thread/INFO]: Generating keypair
[16:37:35] [Server thread/INFO]: Preparing start region for dimension minecraft:overworld
[16:37:35] [Render thread/INFO]: Preparing spawn area: 0%
[16:37:35] [Render thread/INFO]: Time elapsed: 252 ms
[16:37:35] [Server thread/INFO]: Changing view distance to 12, from 10
[16:37:35] [Server thread/INFO]: Changing simulation distance to 12, from 0
[16:37:36] [Server thread/INFO]: testuser[local:E:b09970f6] logged in with entity id 99 at (5.87454050217034, 78.0, -1.1730405160678463)
[16:37:36] [Server thread/INFO]: testuser joined the game
[16:37:36] [Render thread/INFO]: Loaded 2 advancements
[16:37:46] [Server thread/INFO]: Saving and pausing game...
[16:37:46] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:overworld
[16:37:46] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_end
[16:37:46] [Server thread/INFO]: Saving chunks for level 'ServerLevel[New World]'/minecraft:the_nether
[16:37:49] [Server thread/INFO]: testuser lost connection: Disconnected
[16:37:49] [Server thread/INFO]: testuser left the game
This issue, as well as MC-277254, occurs because the reporter is using an unlicensed copy of Minecraft.
@MrMuskle My account is older than 10 years and I'm logged in; please be careful with such accusations.
The log you provided shows your username is testuser. While it is certainly possible that this is your actual username, I am far more inclined to believe this username was provided due to an unlicensed version of the game, or because you are using a modding/testing environment under an 'offline' user account. While you may not have a 'modded' instance (using mods via fabric or forge), bugs are not allowed when reproduced in a non-vanilla (via the official launcher) environment.
I cannot reproduce this issue, and will opt to resolve it as invalid based off the uncertainty around the status of your account and/or game environment. If you can reproduce this issue in 24w40a, in a totally 100% vanilla environment from the official launcher, with a paid version of the game, please create a new report with a video showcasing you reproducing the bug with F3 open with proof that you are playing from Vanilla.
@[Helper] Jingy What I did was a sanitization - It's none of your business what my account is called like. As already said before, I'm using a valid, paid and neutral account for that.
And again: As already said before, I'm using an unmodded/"unmodified" Version (vanilla) of Minecraft. If you cannot reproduce the bug - okay - but think twice before accusing me about using an illegal version. One can be prosecuted for that, especially since it is known that there is NO illegal activity involved here.
–
And one big advice to all so called "helpers" volunteers in Mojang's Bugtrackers: Do NOT shoot the messenger.
Can you please provide a video showcasing the bug?