1.15.2, 1.16 Pre-release 2, 1.16 Pre-release 3, 1.16 Pre-release 4, 1.16 Pre-release 6, 1.16 Pre-release 7, 1.16 Pre-release 8, 1.16 Release Candidate 1, 1.16, 1.16.1, 20w27a, 20w28a, 20w29a, 20w30a, 1.16.2 Pre-release 1, 1.16.2 Pre-release 2, 1.16.2 Release Candidate 1, 1.16.2 Release Candidate 2, 1.16.2, 1.16.3 Release Candidate 1, 1.16.3, 1.16.4 Pre-release 1, 1.16.4 Pre-release 2, 1.16.4 Release Candidate 1, 1.16.4, 20w46a, 20w48a, 20w49a, 21w03a, 1.16.5, 21w05a, 21w05b, 21w06a, 21w07a, 21w11a, 1.17, 1.17.1 Pre-release 1, 1.17.1, 21w37a, 21w41a, 21w44a, 1.18 Pre-release 1, 1.18 Pre-release 4, 1.18 Release Candidate 1, 1.18, 1.18.1, 22w11a, 22w13a, 22w16b, 1.19, 1.19.1 Release Candidate 1, 1.19.1 Pre-release 2, 1.19.1 Pre-release 4, 1.19.2, 22w45a, 1.19.3, 23w07a
Since 1.13, the RAM used by the game has increased drastically to reach more than 5 GB in 1.15.2 and higher when Minecraft is not limited by JVM default arguments (= put -Xmx8G for example)!
For comparison, 1.12.2 uses only 500 MB of RAM!
This problem is apparently due to the DataFixerUpper introduced in 1.13.
How to test
- Go to the "Installations" section of your Minecraft launcher.
- Click on the three dots that appear when you hover over the profile you want to use for this test, and then click "Edit". If you don't already have a profile, create one!
- Select the version you want to test.
- Click on "More Options"
- Change the "-Xmx" argument in the "JVM Arguments" section to allocate 6 GB of RAM or more. Example for 8 GB (recommended) : -Xmx8G
- Save your profile.
- Open the task manager of your operating system.
- Launch the game with the correct profile and observe the evolution of the RAM used by the game in the task manager.
- Repeat for each version you want to test.
Here are all the tests I did from 1.12.2 to 1.16 Pre-Release 2, on all stable versions of Minecraft.
I have allocated 8 GB of RAM each time so as not to restrict the game to too low a ceiling, which would not allow us to see the problem.
No other programs run on the PC (except Discord and my recording program).
I did the test on my two different machines and the results are the same.
- Minecraft 1.12.2 (~450 MB) : Client RAM Test 1.12.2.mp4
- Minecraft 1.13.2 (~2.1 GB) : Client RAM Test 1.13.2.mp4
- Minecraft 1.14.4 (~5.0 GB) : Client RAM Test 1.14.4.mp4
- Minecraft 1.15.2 (~5.2 GB) : Client RAM Test 1.15.2.mp4
- Minecraft 1.16 Pre-Release 2 (~5.2 GB) : Client RAM Test 1.16 Pre-2.mp4
We can also observe that with each new version, the CPU is used harder and harder, even after the game is fully loaded (especially in 1.16).
This ticket is attached to MC-190258 which processes the server side.
- is duplicated by
MC-191755 Possible Memory Leak issue with update 1.16
MC-193261 Java memory garbage collection bug
MC-236128 RAM maxed out on 1.17.1 causing crashes
MC-259868 Minecraft Using WAY Too Much Memory
- relates to
MC-173001 Memory issues / leaks in POI manager and lighting engine when loading chunks
MC-185263 Non full chunks in cache memory "semi-leak"
MC-202953 DataFixerUpper on startup causes excessive CPU usage
MC-190258 Abnormally very high RAM usage since 1.13 (server side)