I don't know whether it is possible to reproduce this.
This happened before the crash:
I wanted to purchase a Realm (for the first time), so I opened the Minecraft Realms Menu and used the link to go to the website; leaving the game open.
After the purchase was finished the menu in-game had been updated and invited me to create a new Realm. After I clicked on the text the game crashed with an IndexOutOfBounds Exception.
After restarting the game the issue didn't happen again.
Stack trace
1.14.4\: [^crash-2019-11-01_01.19.00-client.txt]
Description: mouseClicked event handler
java.lang.IndexOutOfBoundsException: Index 1 out-of-bounds for length 1
at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:248)
at java.base/java.util.Objects.checkIndex(Objects.java:372)
at java.base/java.util.ArrayList.get(ArrayList.java:440)
at cvi$d.selectItem(SourceFile:1106)
at cvi$d.mouseClicked(SourceFile:1084)
at net.minecraft.realms.RealmsObjectSelectionListProxy.mouseClicked(SourceFile:83)
at dad.mouseClicked(SourceFile:27)
at net.minecraft.realms.RealmsScreenProxy.mouseClicked(SourceFile:226)
at cyd.b(SourceFile:86)
at dcl.wrapScreenError(SourceFile:441)
at cyd.a(SourceFile:86)
at org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:36)
at org.lwjgl.system.JNI.invokeV(Native Method)
at org.lwjgl.glfw.GLFW.glfwPollEvents(GLFW.java:3101)
at cuo.k(SourceFile:408)
at cuo.c(SourceFile:279)
at cyc.b(SourceFile:1023)
at cyc.e(SourceFile:976)
at cyc.b(SourceFile:410)
at net.minecraft.client.main.Main.main(SourceFile:155)Attachments
Comments 3
I think the problem with this crash is that my preconditions a very hard to reproduce. The only idea I would have is to cancel the realm and reorder it but that would most likely cost money every time. I would have hoped that a developer could recreate the preconditions without these restrictions. I don't even know whether it's possible to start from scratch and get to the state that maybe required to trigger this crash.
I would guess that some internal List doesn't get updated with the GUI and the GUI tries to lookup an entry that does not exist in this List.
I don't know whether the resource pack could be responsible for the crash: wouldn't a problem with resources have manifested again after the game had been restarted?
And a problem with Java10 would most likely manifested in the module system, wouldn't it? As far as I know the JVM has a backwards-compatibility mode for code compiled for an older version.
But I'm not very sure about that. Maybe a developer could help.
Does this issue occur when using Java 8? Only this version is officially supported for the game, currently.
Also, is there any impact when disabling the resource packs you have installed?