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

Possible chunk corruption - crash bug

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.8, Minecraft 1.8.1
    • None
    • Envoushost server hosting - I do not have any details about the environment the server is running in.
    • Unconfirmed

      My server has an error/crash bug. It appears to affect a particular part of the world. It took me a while to figure this out as the anomaly/glitch/whatever was in the spawn chunks. Moving the spawn point several hundred meters away fixed the problem EXCEPT when the glitched area is loaded.

      Futhermore, I have tracked the location and last known direction of movement of player entities when crashes occur and charted them. From this data, it looks like this crash happens when the affected chunk or chunks load(s) or unload(s). I believe this to be a sort of world file, chunk, or block corruption.

      I currently have no other information about the nature or cause of this corruption.

      This issue began affecting the server immediately after updating to release 1.8

      There are two distinctly different errors in the enclosed crash logs, and they appear to alternate.

        1. crash-2014-12-04_07.36.06-server.txt
          1 kB
          Valiant Seventy
        2. crash-2014-12-04_07.36.47-server.txt
          6 kB
          Valiant Seventy
        3. crash-2014-12-04_07.39.29-server.txt
          3 kB
          Valiant Seventy
        4. crash-2014-12-04_07.40.23-server.txt
          5 kB
          Valiant Seventy
        5. crash-2014-12-04_07.44.33-server.txt
          1 kB
          Valiant Seventy
        6. crash-2014-12-04_07.45.27-server.txt
          6 kB
          Valiant Seventy

            Unassigned Unassigned
            Valiant70 Valiant Seventy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: