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

Beacon effect crashes client to desktop

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: Minecraft 1.13-pre3
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Windows 10, 64bit
      Java 1.8.0_25, 64bit
    • Confirmation Status:
      Unconfirmed

      Description

      Activating beacon effect crashes the game to desktop, when player opens inventory for a first time.

      What I expected to happen was...:
      Activate beacon, open inventory to check the effect if it's working or not.

      What actually happened was...
      After pressing inventory button, game crashes to desktop

      Tried with 3 and 4-tier beacon pyramid.

      Steps to Reproduce:
      1. Construct a beacon pyramid
      2. Place beacon, choose effect and power it. (In my case: Haste at fistrs, Haste II later again)

      3. Open inventory... crash.

       

      There is a workaround: to get it to work:

      1: After beacon activation, wait until your world's autosave kicks in.

      2: Open inventory - game crashes.

      3: If you have waited enough, your game will be autosaved after beacon activation and the effect is working as usual. Open your inventory works as intended. Happy playing!

       

      Just for reference, here are my client's JVM arguments:

      -Xmx8G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                danmama Danmama
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: