I started up a new hardcore world in 21w44a, and very early on (first day still) I was chopping down trees when suddenly my game froze with a message in the lower right corner of the screen "Saving world". My CPU fans spun up to 100%. It just hung with an occasional spinning wait mouse cursor, and then eventually it offered up a screen telling me that the Java VM had run out of memory and that I could try returning to the title screen or quit the game.
I returned to the title screen and attempted to load the same world again and it just started doing the same thing and also spinning the fans up to 100% again.
I then restarted the game entirely and attempted to load the same world again and the exact same thing happened. I thought you guys might want to look at the world, so decided to hop on here and file a report. A casual search didn't seem to locate anything recent.
I started up a second world with the exact same results, except the game just crashed with no message eventually.
Update: I was able to get back into my existing worlds after modifying the Java arguments to specify more memory (I changed the -Xmx2G to -Xmx16G).
Linked issues
is duplicated by 1
Attachments
Comments 4
There didn't seem to be any crash reports available. There were a couple of logs, although I don't see anything obvious. Let me know if you'd like me to reproduce the bug to get additional info. I'll also include the logs when trying to get into each game after restarting.
2021-11-06-1 is the first time it happened
2021-11-06-2 is my attempt to load it after it restarted
2021-11-06-3 is the second time
2021-11-06-4 is my attempt to load that
See MC-239682. This bug report is either related or a duplicate.
When the game runs out of memory, the behaviour of the game is unpredictable. This makes obtaining a crash report unreliable.
Information that may be helpful: render distance, simulation distance.
Thank you for your report!
We're tracking this issue in MC-239682, so this ticket is being resolved and linked as a duplicate.
That ticket has already been resolved as Fixed. Please check the Fix Version/s field in that ticket to see in which version this behavior was or will be fixed.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
-- I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
Please attach the crash report or log. The crash report is a text file located in the
[.minecraft|https://minecrafthopper.net/help/finding-minecraft-data-folder/]/crash-reports folder namedcrash-date-client.txt. If not available attach thelauncher_log.txtfile.