mojira.dev
MCPE-229864

Naturally generated lava causes memory leak / excessive RAM usage

Steps to reproduce:

  • Create a new world with seed 8104515, creative, simulation distance 6

  • Teleport to 0 90 -735 in the nether (/execute in nether run tp @s 0 90 -735)

  • Observe Minecraft memory usage (My base memory usage in tests started at 1.7gb)

  • Stay in area and let world run for 1 hour

  • Observe Minecraft memory usage (Frequent spikes in memory usage in excess of 5gb)

Expected result:

  • Minecraft stays near baseline memory usage (1.7gb)

Actual result:

  • Minecraft has excessive memory usage, frequently fluctuating from 2gb-5gb

Additional information:

  • This appears to be caused by a naturally generated lava source created at world generation located at -4 107 -735

  • Removing the lava source does not remove all the child lava created by the source and memory issues persist

  • World size increases to 200mb after 1 hour of playtime

  • This effects any player that has loaded this area in the nether

  • When any player loads the nether, even when not local to this area; fluctuations in memory usage are observed

  • Excessive memory usage can be stopped by deleting a 4x4 chunk area centered around this lava source, encompassing all child lava flows

  • Memory leak will return after regeneration of this area

This bug would be extremely difficult for the average Minecraft player to identify and can be world ending. On a multiplayer server, this bug is amplified by each player who has loaded the effected area; leading to server instability and crashes.

Attached to the bug report is a screenshot of the high RAM usage, pictures of the suspect lava, and a 1 hour test of the world from new where I stayed in creative in the nether at this location.

Linked issues

Attachments

Comments 3

This was automatically Resolved as Duplicate? Is there a link to the bug report this is being tracked in?

No, it was resolved manually by a moderator. Only the comment informing you that the report has been resolved is automated.

This issue is being tracked at MCPE-224638 . You can find the link to the report by clicking on the Issue Links Panel button on the right, but it is currently having issues loading.

Thank you, Ocelot!

Squee

(Unassigned)

Unconfirmed

Windows

1.21.114 Hotfix

Retrieved