Minecraft
  1. Minecraft
  2. MC-108358

Crash when 32 or more pistons retract in a single chunk (IllegalArgumentException)

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: Minecraft 16w40a
    • Fix Version/s: Minecraft 16w41a
    • Security Level: Minecraft - Public (Viewable by everyone)
    • Labels:
      None
    • Confirmation Status:
      Community Consensus

      Description

      This crash occurs when 32 or more pistons retract in a single chunk. To reproduce the crash you can use the linked world. Just walk on the pressure plates twice. On closing the door the game crashes.

      World download: http://www.mediafire.com/file/qy93ac93thos4k3/Fastest+4x4+%281_8+%29%282%29.zip
      (World by DicoTheRedstoner: https://www.youtube.com/watch?v=euLCroOrAvU)

      Description: Ticking entity
      
      java.lang.IllegalArgumentException: Cannot set property ats{name=extended, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in ath{block=minecraft:air, properties=[]}
      	at ath$a.a(SourceFile:176)
      	at ata.a(SourceFile:291)
      	at asz.a(SourceFile:152)
      	at ath$a.a(SourceFile:388)
      	at ajn.a(SourceFile:1009)
      	at sk.d(SourceFile:580)
      	at bpn.d(SourceFile:866)
      	at st.g(SourceFile:1570)
      	at aau.g(SourceFile:1546)
      	at st.n(SourceFile:1855)
      	at aau.n(SourceFile:515)
      	at bpn.n(SourceFile:823)
      	at st.A_(SourceFile:1688)
      	at aau.A_(SourceFile:270)
      	at bpn.A_(SourceFile:184)
      	at ajn.a(SourceFile:1533)
      	at ajn.g(SourceFile:1511)
      	at ajn.k(SourceFile:1394)
      	at ben.t(SourceFile:1649)
      	at ben.av(SourceFile:967)
      	at ben.a(SourceFile:395)
      	at net.minecraft.client.main.Main.main(SourceFile:124)
      
      1. crash-2016-10-06_20.19.57-client.txt
        4 kB
        Panda
      2. crash-2016-10-06_21.55.39-client.txt
        4 kB
        Meri Diana
      1. 2016-10-07_11.13.27.png
        490 kB

        Issue Links

          Activity

          Hide
          Xavom added a comment - - edited

          Confirmed. I have a world that uses a decent amount of pistons as this does. I've removed redstone until the world no longer crashes, and when adding just 1 redstone (dust, repeater, comparator) that gets updated, not even powered, the world cashes. My last crash killed the world. Restore time...

          http://imgur.com/MsTwOXB
          Adding the repeater at the crosshair in the center of this picture, then activating the machine, the world crashes. Redstone wire has been removed where shown in an attempt to isolate.

          Show
          Xavom added a comment - - edited Confirmed. I have a world that uses a decent amount of pistons as this does. I've removed redstone until the world no longer crashes, and when adding just 1 redstone (dust, repeater, comparator) that gets updated, not even powered, the world cashes. My last crash killed the world. Restore time... http://imgur.com/MsTwOXB Adding the repeater at the crosshair in the center of this picture, then activating the machine, the world crashes. Redstone wire has been removed where shown in an attempt to isolate.
          Hide
          Meri Diana added a comment -

          A Redstoner called Robobrine sent me his missile factory that contains also pistons.
          In 16w40a it crashes, in the previous 1.11 snapshots it doesn't.

          If you relog into the world after the crash, you'll continue to crash.

          Crash log attached, untouched/not-yet-crashed worldsave also attached.

          Steps to reproduce the crash
          Simply open up the world in 16w40a and hit the button to the very left, wait for a few seconds.

          Show
          Meri Diana added a comment - A Redstoner called Robobrine sent me his missile factory that contains also pistons. In 16w40a it crashes, in the previous 1.11 snapshots it doesn't. If you relog into the world after the crash, you'll continue to crash. Crash log attached, untouched/not-yet-crashed worldsave also attached. Steps to reproduce the crash Simply open up the world in 16w40a and hit the button to the very left, wait for a few seconds.
          Hide
          [Helper] Marcono1234 added a comment -

          Might relate to MC-107543, the title is misleading but it tried to get there a property of an air block whereas here it tries to set one.

          Show
          [Helper] Marcono1234 added a comment - Might relate to MC-107543 , the title is misleading but it tried to get there a property of an air block whereas here it tries to set one.
          Hide
          Xavom added a comment - - edited

          I've noticed that while I can trigger 48 pistons without a crash, triggering 22 sticky pistons with blocks does. Added screenshot and world download (16w40a Crash Test) as attachments.

          Show
          Xavom added a comment - - edited I've noticed that while I can trigger 48 pistons without a crash, triggering 22 sticky pistons with blocks does. Added screenshot and world download (16w40a Crash Test) as attachments.
          Hide
          G4me4u added a comment - - edited

          Turns out, the bug is very easy to recreate from scratch. It turns out, that if you simply build a grand wall of around 70 or so pistons and power them all, the client will crash, when you unpower them. If you wanna recreate this bug, you can download the attachment ("Piston Crash Demo") and flick the lever, to turn off all the pistons. If the bug does not appear, you can add more pistons to stress the packets even more.

          There can be multiple reasons for this, but from my perspective, I'd say that the pistons are simply creating so many packets, that the client get's out of sync with the server. When this happens, the tileentity might not have been deleted or the block might not have been set before the next gametick. This will cause the tile-entity to look at a blockstate on an airblock rather than the actual moving tile (as it's not been updated on the client yet).

          Show
          G4me4u added a comment - - edited Turns out, the bug is very easy to recreate from scratch. It turns out, that if you simply build a grand wall of around 70 or so pistons and power them all, the client will crash, when you unpower them. If you wanna recreate this bug, you can download the attachment ("Piston Crash Demo") and flick the lever, to turn off all the pistons. If the bug does not appear, you can add more pistons to stress the packets even more. There can be multiple reasons for this, but from my perspective, I'd say that the pistons are simply creating so many packets, that the client get's out of sync with the server. When this happens, the tileentity might not have been deleted or the block might not have been set before the next gametick. This will cause the tile-entity to look at a blockstate on an airblock rather than the actual moving tile (as it's not been updated on the client yet).
          Hide
          DJ added a comment -

          I have done some testing and concluded that this is chunk based. The bug is only caused when 32 or more pistons retract at the same time in the same chunk. So you can have as many pistons retracting as you want as long as there is less than 32 per chunk.

          Show
          DJ added a comment - I have done some testing and concluded that this is chunk based. The bug is only caused when 32 or more pistons retract at the same time in the same chunk. So you can have as many pistons retracting as you want as long as there is less than 32 per chunk.
          Hide
          [Mod] Neko added a comment -

          Updated ticket with new information, thanks!

          Show
          [Mod] Neko added a comment - Updated ticket with new information, thanks!

            People

            • Assignee:
              [Mojang] Grum (Erik Broes)
              Reporter:
              Panda
            • Votes:
              21 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                CHK: