Uploaded image for project: 'Spigot'
  1. Spigot
  2. SPIGOT-4780

CLONE - Chunk Loading Errors on 3 Different Servers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Major Major
    • None
    • None
    • git-Spigot-47463c2-6de3aa1 (MC: 1.14)
    • N/A
    • Yes

      BUG REPORT INSTRUCTIONS:
      1. This did not occur on a Vanilla server test.
      2. Tested on the latest 1.14 rev from the buildtools
      3. No open versions of this bug can be seen in the provided list relevant to this visual issue specifically (https://hub.spigotmc.org/jira/issues/?filter=12200)
      4. This bug is specific to SPIGOT 1.14 by our testing. We do not run craftbukkit.
      5. REPRO STEPS:

      Spawn into a new 1.14 spigot world, start flying in a straight line (any direction, it doesn't matter) for about 500-100 blocks. As you start to go further and further from spawn (still only maybe 20 chunks away though in the screenshot below) the server very clearly starts to load chunks randomly. This may start to occur in previously loaded/built in chunks following the first signs of the problem.

      Past a certain point the world may completely stop rendering or loading chunks, but will render mobs still, leaving them floating in space above a void. The server is not throwing any "can't keep up" messages or timing errors, nor is it pulling heavy resources.

      6. There are no plugins installed
      7. Not an API Bug
      8. Feature Request

      Max resource usage on the local server was about 20% CPU and 2GB ram, even while I was flying to new chunks.

      The pictures demonstrate the error, including an example where a chunk right below the player is unloaded. The first is maybe 200 blocks away from spawn using the Reproduction method. IĀ also included a video of the repro method, flying away from spawn and finding unloaded areas.

            Unassigned Unassigned
            AdmiralRadish Nick S
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: