Started a new world. Went exploring around the desert I spawned in. After a about a half hour I made a boat to explore across the ocean - was starting to cross a warm ocean with lots of coral and performance dropped considerably. I went forward for a while not coming near the chunks loading and I stopped to let the game catch up, after a minute or so I went to proceed and realized minecraft had frozen. Waiting longer didn't help. I had to forcibly close it and got a 0 error in the launcher about minecraft crashing. Tried reloading and minecraft opens up and freezes immediately after the world loads. Rebooting my laptop and the same thing still happens.
More Info:
Migrated Microsoft Minecraft account.
Not using the newest launcher.
Laptop Specs:
Windows 10 Pro
Intel i7-10870H 2.2ghz
32GB RAM
Nvidia GeForce RTX 3060 Laptop GPU
Attachments
Comments 16
Performance is super bad in this world. I'll try creating a new one and seeing if I have similar results.
I believe this report would benefit from some clear steps to reproduce. Seed and coordinates are needed at a minimum; also try out the steps to reproduce before posting them to see if they are accurate.
I created two worlds and have very similar results where performance turns south to where the game starts pausing/freezing every half a second then gets to the point where the game just completely freezes solid. The best example is the origonal world I created. Seed: 7377209451618990386 Coords of the large warm ocean with coral where the worst performance happens: -28/81/121 (Just south of the spawn area).
See attached screenshots for seed and coords.
The latest snapshots are known to play slowly and eventually run out of memory when terrain is generated. This is logged as MC-239682.
Ways to mitigate this until the bugs are fixed:
Allocate more RAM to Minecraft in the JVM options. 1GB can be used for testing but choppy performance will be evident from the start. That is not recommended for single player. 2GB is a minimum for normal play and is what I use for testing. 4GB is better. This option is -Xmx.
Check your JVM options for memory management. The Garbage First Garbage Collector (G1GC) should be used with Minecraft because that allows garbage collection to be configured so lag spikes are less frequent. My G1GC settings are:
-Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
A good explanation of configuring G1GC with Minecraft servers can be found here: https://forums.spongepowered.org/t/optimized-startup-flags-for-consistent-garbage-collection/13239
I was able to escape by switching to spectator and tping out of there as soon as the world loaded. Seems there is a performance issue with warm oceans - this one is massive. I'll update with seed and coords soon.