When trying to ''Quit Game", the screen freezes, and it is necessary to use Task Manager and kill the session. Upon doing so, the Java engine throws a non-specific error, and the return to the launcher shows that an error occured. This happens using either OpenJava RT, or the standard Java RT, 64-bit. This is on a vanilla version of 1.17, on a new world or a pre 1.17 world.
Attachments
Comments 9
It is showing that it is set to 3, which is the default. Worlds behave normally, they just won't quit without freezing. Please note the correction, it is on "Quit Game", not "Save and Quit to Title".
Windows 7 Ultimate (Version 6.1 - Build 7601 - SP1) - 64 bit
AMD A8-5500 APU 3.20 GHz
NVIDIA GeForce GTX-1050
16GB ram
FYI - All previous versions are working fine, same launcher. Just the 1.17 is doing this. I didn't try any of the pre-releases.
Does your screen get stuck on "saving world"? (MC-148866)
No, it saves the world, either single or multi just fine. It is only when I choose 'Quit Game' that it freezes.
If MC-148866 doesn't describe your issue, please could you attach the crash report which can be found in minecraft/crash-reports/crash-<DATE>-client.txt. If for some reason you cannot provide this, please attach the full launcher log which can be found in minecraft/launcher_log.txt. Supplying the team with this information would help them to determine what the problem is. Thanks 🙂
Thank you for your report!
However, this issue is Invalid.
Your game, launcher or server is modified.
If you can reproduce the issue in a vanilla environment, please recreate the issue.
Any non-standard client/server/launcher build needs to be taken up with the appropriate team, not Mojang.
Any plugin issues need to be addressed to the creator of the plugin or resource pack.
If you have problems on large servers, such as The Hive and Hypixel, please contact them first as they run modified server software.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
In the world that this issue occurred in, what was the "
randomTickSpeed" gamerule set to?