Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-141622

Frame Time Spikes and Garbage Collection issues when Close to Large Amounts of Bamboo

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 18w50a
    • None
    • MacOS 10.13.6, Java 1.8 (bundled w/ MC)
    • Unconfirmed

      When close to and looking at a large field of Bamboo, frame time spikes to 300ms or more occur regularly (with frame time dependant on amount of Bamboo), lined up with memory garbage collection (the memory usage goes down corresponding to the spikes). This is even though average frame rate is still close to expected.

       

      Not looking at the bamboo, or being 20-30+ blocks away causes frame time spikes to disappear. This was discovered with growing bamboo, fully grown bamboo does not cause these spikes. Testing with higher random tick speed (and thus higher bamboo growth speed) increases size and frequency of spikes, so the spikes are caused by bamboo growth. Spikes are also observed when harvesting bamboo from a large field of bamboo, or placing or destroying any block in close proximity to a lot of bamboo.

       

      Conjecture: Long frame times are caused by lighting updates and block updates associated with growing large amounts of bamboo in fields, and harvesting bamboo from large fields of bamboo.

       

      This was tested both on a multiplayer server and on a superflat single player world.

       

      Videos (YouTube) of 50x50 field of Bamboo:

      Spikes at normal random tick speed, and showing effects of proximity and facing direction

      Testing 1000 and 100 random tick speed, fully grown bamboo, and harvesting

       

       

       

        1. 2018-12-30_13.19.56.png
          2018-12-30_13.19.56.png
          1.82 MB
        2. 2018-12-30_13.50.43.png
          2018-12-30_13.50.43.png
          553 kB
        3. 2018-12-30_13.50.56.png
          2018-12-30_13.50.56.png
          1.08 MB
        4. 2018-12-30_13.51.03.png
          2018-12-30_13.51.03.png
          1.93 MB
        5. 2018-12-30_13.56.23.png
          2018-12-30_13.56.23.png
          1.16 MB
        6. 2018-12-31_17.50.28.png
          2018-12-31_17.50.28.png
          1.34 MB
        7. 2018-12-31_17.50.28.png
          2018-12-31_17.50.28.png
          1.34 MB
        8. 2018-12-31_17.58.20.png
          2018-12-31_17.58.20.png
          975 kB

            Unassigned Unassigned
            immmabed Brady Coles
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: