Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-184552

High RAM usage! Memory Leak!

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.21.2 Hotfix
    • None
    • Unconfirmed
    • Windows

      The game becomes unplayable due to a memory leak that causes the RAM usage to increase continuously, leading to severe lag. The issue appears randomly and is not reproducible every time. It may be related to Riot Vanguard, as it prevents multiplayer gameplay over Wi-Fi.

      Steps to Reproduce

      1. Launch the Game:
        • Open the game and navigate to the main menu.
        • Observe the RAM usage (it should remain stable while in the menu).
      1. Enter a World:
        • Open a world (single-player or multiplayer server) and play for a few seconds.
        • Monitor the RAM usage, which should start increasing at a rate of approximately 50 MB/s.
      1. Return to Menu:
        • Exit the world and return to the main menu.
        • Check the RAM usage again. It will not decrease and remains at the elevated level.
      1. Re-enter a World or Server:
        • Enter a world or a multiplayer server again.
        • Notice that the RAM usage continues to increase indefinitely.
        • Repeat the process of leaving and re-entering the world or server 3-4 times to temporarily stabilize RAM usage, though the issue may reoccur.

      Expected Result

      • When standing in the main menu, RAM usage should remain stable and not increase.
      • Upon entering and playing in a world or server, RAM usage should increase initially but stabilize and not continue to rise indefinitely.
      • Exiting a world and returning to the menu should cause RAM usage to decrease to normal levels.

      Additional Notes

      • The issue is observed on both servers and single player new MCC Championship event servers and older survival worlds.
      • There may be a connection to Riot Vanguard, as using this software prevents multiplayer gameplay over Wi-Fi however exiting it doesn't appear to fix the issue but fixes the WI-FI Multiplayer issue

      Visual Evidence

      • Refer to the attached images showing the RAM usage behavior:
        1. Standing in the menu (stable RAM usage).
        2. Entering a world (increasing RAM usage).
        3. Exiting the world (elevated RAM usage does not decrease).

       

      This is a serious issue that makes the game unplayable! It's appearing at random not every time! I SUSPECT THAT RIOT VANGUARD HAS SOMETHING TO DO WITH IT! since using that does't allow me to play over the WI-FI multiplayer!

      Standing in the menu stops the RAM to go up!

      Opening a world for a few secconds makes the RAM go up over time with about 50Mb/s

      leaving the world and then standing in the menu will stop that but the memory stays up still! never goes back down! see pictures!

      Entering a world or a server makes the RAM memory go up forever the only fix sometimes is to leave the world or server about 3-4 times then enter again and hope that it's not going up again.

      In the photos below is me playing on the new MCC Championship event server but it's not limited to that my old survival world from v1.15 has the same issue RAM goes up and then everything lags out bad.

        1. Screenshot (167).png
          Screenshot (167).png
          629 kB
        2. Screenshot (166).png
          Screenshot (166).png
          439 kB
        3. Screenshot (165).png
          Screenshot (165).png
          556 kB
        4. Screenshot (163).png
          Screenshot (163).png
          531 kB
        5. Screenshot (162).png
          Screenshot (162).png
          472 kB
        6. Screenshot (161).png
          Screenshot (161).png
          480 kB
        7. Screenshot (160).png
          Screenshot (160).png
          303 kB
        8. Improved Input Response.png
          Improved Input Response.png
          33 kB

            soripop1234 Sori Pop
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: