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

Server crash -> Netty crash? Too much entities?

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.10.2, Minecraft 16w40a, Minecraft 16w41a
    • None
    • Unconfirmed

      What did I do

      I just placed a large amount of gravel and then removed a bit of it.
      Result

      • Windows told me that the client isn't responding anymore.
      • Server told me Client lost connection.
      • Client told me I'm still on the server (had to kill it with the task manager). - Server crashed a bit later.

      What did I do

      • Then I restarted the Server and the Client.
      • I Joined the server and yeah, same stuff happened again. Well, at least the Client was able to be closed with the quit button instead of with the task manager. But the server crashed again.
        I uploaded the picture which Minecraft showed me before the server crashed after I restarted the Server.

      How to fix the world
      From my experience with this problem in Minecraft 1.10.2, download MCEdit and remove the complete chunks or delete the complete world or restart the server several times and hope that it some day works again.

      How to reproduce:
      After reading the log files, it should be clear. Place a lot of gravel or sand and remove some of it, so that everything falls down.

      I hope this crash get's fixed before 1.11.

        1. 2016-10-15_14.31.13.png
          277 kB
          ShadowDragon
        2. 2016-10-15-3.log.gz
          1 kB
          ShadowDragon
        3. crash-2016-10-15_14.19.49-server.txt
          9 kB
          ShadowDragon
        4. crash-2016-10-15_14.31.35-server.txt
          10 kB
          ShadowDragon
        5. latest.log
          2 kB
          ShadowDragon

            Unassigned Unassigned
            ShadowDragon ShadowDragon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: