MultiMC
Minecraft freezes when 'saving world' on 1.20.4 vanilla offline mode
Operating System
Linux
Description of bug
Expected:
- World is saved, user is sent back to main menu
Actual:
- Stuck on 'saving world' screen. Process has to be killed.
Additional info:
Logs.
Does not happen when using normal online launch with the same profile.
Related? https://github.com/MultiMC/Launcher/issues/3620 Facing the same on fabric but created a new instance without any kind of mods to be sure.
java --version output:
openjdk 21.0.2 2024-01-16 LTS
OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13-LTS, mixed mode, sharing)
Platform: Linux Ubuntu 22.04.4 LTS kernel 6.5.0-26-generic
Steps to reproduce
- Create a new clean 1.20.4 vanilla instance
- Launch Offline while changing name (ex. TestName).
- Create a new world with default settings and join it.
- Wait for everything to be loaded, mine 1 dirt block.
- Press 'Esc' -> 'Save and quit to title'.
Suspected cause
No response
This issue is unique
- [X] I have searched the issue tracker and did not find an issue describing my bug.
I saw the discussion on that last issue suggesting that this is purely a game bug. However, I should add that there are definitely launchers out there that don't have this problem (namely TLauncher) so it might be deeper than that.
On the matter of TLauncher I noticed it runs the game with --userType mojang whereas MultiMC does with --userType msa. It might be related or it might not be :) As I haven't found a way to alter these launch params for MMC.
I know one possible cause. Not having enough disk space on the drive the Minecraft install is in. Because there is no space on the disk, it can't save and gets stuck.
This issue is also present with 1.20.6 but I am NOT in offline mode. I am launching Minecraft the normal way and I have waited 30 minutes for my world to save. Just like OP, it is a cloned instance.
This issue is also present with 1.20.6 but I am NOT in offline mode. I am launching Minecraft the normal way and I have waited 30 minutes for my world to save. Just like OP, it is a cloned instance.
Since there is a difference and we need to see the log, it might be a good idea to create your own thread (if you haven't already).
Try using Java 17, since that's what is officially supported.
to answer this, there is no change in behavior with java 17
I know one possible cause. Not having enough disk space on the drive the Minecraft install is in. Because there is no space on the disk, it can't save and gets stuck.
definitely not the case
/dev/mapper/nvme0n1p6_crypt 260G 224G 24G 91% /
strace -f -p 112462 > ./Downloads/strace.txt 2>&1
right before pressing 'save world':
It's definitely doing something (although how the hell did we get to region -20,0 in a world that was just created is anyone's guess):
statx(AT_FDCWD, "/home/gear/.local/share/multimc/instances/1.20.4/.minecraft/saves/New World/region/c.-20.0.mcc", AT_STATX_SYNC_AS_STAT|AT_SYMLINK_NOFOLLOW, STATX_ALL, 0x71ee1107df10) = -1 ENOENT (No such file or directory)
Is the Intel graphics the best you have?
No there's also a 1650ti in this XPS 15 9500 laptop but switching to it doesn't help
I had the same issue, but the solution was a bit strange. I changed my username, but it didn't update within the launcher. As a result, when I tried to save the world, Minecraft got confused because it didn’t know how to process the change. Here's my explanation: When using an official Microsoft account, I believe there’s a token somewhere that uses your username as a parameter. To fix this, you need to log out and then log back in so that the changes are properly updated, and you can start playing again. Keep in mind that this is only if you have an official account, not "no premium".
