Uploaded image for project: 'Bedrock Dedicated Server'
  1. Bedrock Dedicated Server
  2. BDS-17527

Multiple server crashes due to memory leak when loading chunks


    • Icon: Bug Bug
    • Resolution: Fixed
    • 1.20.30
    • 1.19.20, 1.19.21 Hotfix, 1.19.30, 1.19.31 Hotfix, 1.19.41, 1.19.63, 1.20.12 Hotfix
    • OS = Debian GNU/Linux 10 (Buster)
      Kernel = Linux 4.19.0-13-cloud-amd64
      Server hosted on a 3rd-party VPS
    • Community Consensus
    • 881031

      Server is running mostly default survival settings except for simulation distance of 6 and chunk render distance of 32. Has been stable for the past year without issue until around 1 month ago. At first we believed the crashes to be caused by entering portals too quickly (going from nether to overworld, then overworld to end portal fast) since some of the crashes were occurring under those conditions, but we have also been getting crashes throughout normal gameplay, when performing normal actions such as placing blocks or even walking around. The crashes occur in multiple areas, overworld, nether, and end. There doesn't seem to be a specific chunk or groups of chunks causing this since the same areas may be fine one moment, then crash at another. As of now the server will crash at least 4-5 times a day if people are active. Checking memory usage showed a steady usage of around 700MB our of the 3GB allocated, so there doesn't seem to be any issue there.

      Made the bug public and removed the world file since I confirmed the memory leak occurs with a fresh world. Also adding some extra info from my comments below:

      After further testing this seems to be a memory leak related to chunk loading. If you check the memory while standing still, not loading chunks, it should be stable. When you load chunks, whether it's via crossing portals, flying, etc. the memory use increases and not come back down, which it should not be doing. Running farms while standing still did not affect the memory usage for us. Passive mob farms, redstone mechanisms, etc. did not contribute to the memory leak. Here's a log of our memory use up until the server crashed again.

      Crash reports are fairly limited in information, but here are some of them attached below.

        1. bds-smaps-15teleportevents.txt
          195 kB
        2. bds-smaps-launched.txt
          187 kB
        3. bds-smaps-userloggedin.txt
          192 kB
        4. heap.dump.gz.partaa
          10.00 MB
        5. heap.dump.gz.partab
          10.00 MB
        6. heap.dump.gz.partac
          2.28 MB
        7. image-2022-09-07-09-50-29-828.png
          43 kB
        8. image-2022-09-09-07-30-54-970.png
          36 kB
        9. pidstat.txt
          63 kB
        10. RamGraph.PNG
          96 kB
        11. RamGraph2.PNG
          164 kB
        12. RamGraph3.PNG
          123 kB
        13. Screenshot_20230510_165647_Chrome.jpg
          548 kB
        14. server_log.txt
          3 kB
        15. Server_RAM.PNG
          29 kB
        16. server.properties
          5 kB
        17. server-1.properties
          0.9 kB
        18. Server Files.PNG
          Server Files.PNG
          95 kB
        19. syrupy_20220827204110.ps.log
          564 kB
        20. TRS.2022.
          4 kB
        21. TRS.2022.
          5 kB
        22. TRS.2022.
          5 kB
        23. TRS.2022.
          19 kB
        24. TRS.2022.
          3 kB
        25. TRS.2022.
          10 kB
        26. TRS.2022.
          4 kB

            Unassigned Unassigned
            Mistahtokyo MaladjustedPlatypus
            83 Vote for this issue
            44 Start watching this issue