-
Bug
-
Resolution: Duplicate
-
None
-
1.20.1, 1.20.2
-
OS: 6.4.10-zen2-1-zen ArcoLinux (not exclusive to arch maybe, as in it affects any distro of linux, not sure if this happens on Windows, one of the bug reports mentioned says they were using windows 10)
Java: Java17.0.1+12, Java17.0.8, Java20.0.2, Java20.0.2.u9-3, Java1.8.0_312-b07 (Java versions I have tested)
Launcher: Official Minecraft Launcher(tested once), GDLauncher(The rest of the time)OS: 6.4.10-zen2-1-zen ArcoLinux (not exclusive to arch maybe, as in it affects any distro of linux, not sure if this happens on Windows, one of the bug reports mentioned says they were using windows 10) Java: Java17.0.1+12, Java17.0.8, Java20.0.2, Java20.0.2.u9-3, Java1.8.0_312-b07 (Java versions I have tested) Launcher: Official Minecraft Launcher(tested once), GDLauncher(The rest of the time)
-
Unconfirmed
-
Performance
EDIT: Make sure to update your java version, I had an older version for java 17, it greatly helps
SIDE NOTE: MINECRAFT STILL USES MORE MEMORY THEN ALLOCATED, BUT I NO LONGER HAVE MEMORY LEAKS.
Also, apologies to the staff, I did not intend to reopen this report, apologies
Bug: Not sure about any other OS, but on arch linux, memory usage is going past the allocated amount and rendered chunks aren't unloaded from memory leading to minecraft consuming all your memory if you load enough chunks.
Steps to reproduce: Im on arch linux, don't know if this will work for other OS. Load any world and start loading/rendering chunks that haven't been loaded onto the memory. (e.g flying in a straight line). The chunks have to be rendered in order to recreate it.
Observed Result: Memory usage starts to go up past the allocated memory and chunks aren't unloaded from memory.
Expected Result: Memory won't go over the allocated limit and chunks should be unloaded from memory when not rendered.
- duplicates
-
MC-173001 Memory issues / leaks in POI manager and lighting engine when loading chunks
- Reopened