-
Bug
-
Resolution: Fixed
-
1.16 Pre-release 1
-
None
-
Confirmed
-
Crash, World generation
-
Very Important
In the Experimental Settings load menu, if I click 'Backup & load', I crash with this error:
Test world
Stack trace
Description: mouseClicked event handler java.lang.IllegalStateException: Lock is no longer valid at daa$a.i(SourceFile:297) at daa$a.h(SourceFile:431) at dtv.a(SourceFile:176) at dlt.a(SourceFile:1850) at dph.c(SourceFile:42) at dne.b(SourceFile:33) at dmy.a(SourceFile:16) at dnc.a(SourceFile:149) at doa.a(SourceFile:27) at dlu.b(SourceFile:92) at dqn.a(SourceFile:431) at dlu.a(SourceFile:92) at dlu.c(SourceFile:162) at amk.execute(SourceFile:94) at dlu.b(SourceFile:162) 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:3050) at com.mojang.blaze3d.systems.RenderSystem.flipFrame(SourceFile:99) at dgu.e(SourceFile:301) at dlt.e(SourceFile:1035) at dlt.d(SourceFile:648) at net.minecraft.client.main.Main.main(SourceFile:215)
- is duplicated by
-
MC-187369 Newly created world crashes after being reopened: Lock is no longer valid
- Resolved
-
MC-187397 All worlds are corrupted; reloading a world created in the latest snapshot shows a warning and may crash the game
- Resolved
-
MC-187418 Inability to load 1.16 pre-release worlds after closure
- Resolved
-
MC-187570 Entirely different chunks load after re-entering game
- Resolved
-
MC-187588 Suddenly crash
- Resolved
- relates to
-
MC-177491 "Lock is no longer valid" crash after updating world from 20w13b->20w14a
- Resolved
-
MC-181833 Crash on world startup after playing world in 20w18a
- Resolved