How to reproduce:
Step 1: Do something for a while, Watch YouTube, Play Roblox.
Step 2: Load up Minecraft and create a new world
Expected Result:
Minecraft works normally
Actual Result:
A suspected "Bad Chunks" issue causes the game to be nearly unplayable
Temporary Workaround:
Restart your PC and run Minecraft before doing anything else
Attachments
Comments 8
We do not have enough information to find the cause of this issue.
While the lag occurs, please press F3
+ L
once, then wait a short moment until profiling has finished.
Afterwards, please attach the generated .zip
file containing the profiling results here. The file path is shown in chat; the file can be found in [minecraft/debug/profiling/<DATE>.zip|https://minecrafthopper.net/help/finding-minecraft-data-folder/]
.
If you are playing on a server please additionally run the command /perf start
to create a profiling report for the server. In case you do not have the permission to run this command, make sure that you're a server operator.
Once profiling has finished, please attach the generated .zip
file from debug/profiling/<DATE>.zip
of the server folder.
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
I will try my best, It sometimes works just fine or it lags like crap, if it does I will get the profiler file
UPDATE: Its probably not a memory leak but the "bad chunks" issue from 2009 where it lags tremendously when loading new chunks
I have noticed that the game has been running out of memory A LOT lately compared to previously when doing other things in 1.19.4 and in 1.20 snapshots, no matter how much memory you allot to the game. I have tried 2 GB to 5 GB and it still runs out of memory. I thought it was my GPU but my GPU will be like 26% or something but the game will be super laggy.
I can't confirm for 100% sure that this is caused by a memory leak but I have noticed what you described.