mojira.dev
MC-138077

Crash - Ticking block entity - When upgrading old 1.12 world to 1.13.2

When I open my old world in 1.13.2 it crashes after ca. 0.5 seconds.

18w43c: [^crash-2018-10-26_17.32.21-server.txt]

Description: Ticking block entity

java.lang.IllegalArgumentException: Cannot get property bmy{name=enabled, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in Block{minecraft:netherrack}
	at blx.c(SourceFile:95)
	at bkt.a(SourceFile:138)
	at bkt.Z_(SourceFile:129)
	at aza.n_(SourceFile:1060)
	at tz.n_(SourceFile:293)
	at net.minecraft.server.MinecraftServer.b(SourceFile:738)
	at net.minecraft.server.MinecraftServer.a(SourceFile:664)
	at djq.a(SourceFile:125)
	at net.minecraft.server.MinecraftServer.run(SourceFile:568)
	at java.lang.Thread.run(Unknown Source)

Linked issues

Attachments

Comments

marcono1234

Could you please attach the 1.12 world or upload it somewhere and share the link? If you are uncomfortable with publicly sharing it, you can first change the "Security Level" of this report to "private".

Cultist_O

I have also been having this issue. I originally posted it as  MC-134542 but that was marked as a duplicate of MC-135453, which was then marked as fixed. I am still having the issue however.

Crash report attached, but my world file is too large, so is linked below.

[media]

Edit: dropbox link to world file

Please let me know when I can remove the world file, as I have limited space available.

marcono1234

Attached crash reports by @unknown, which were originally attached to MC-135453.

marcono1234

Attached @unknown's world (comment with most of the files which are not hopefully needed stripped out.

  • World:

[media]
  • Crash report:

[media]

Additionally the warning "Block Entity was expected to be a chest" was logged. @@unknown, did you see this warning as well? And could you please still leave the world in your dropbox for now.

Cultist_O

I do also see the expected chest warning (x7), (I had assumed they would be in the crash report.)

Also, I can leave the world file there as long as it's actually useful, just please let me know when it's no longer needed.

Cultist_O

Still affects 18w49a btw

Adrian Östergård

Is this still an issue in 19w11b?

hoyskedotte

I tried again in 19w11b and the game still crashes. But this time I get ticking world crash. (New crashlog provided) As a workaround i can restart the game, and try again and the game will not crash in that area. It will still crash if i move towards my base ie.
The game feels in general very laggy (speed of chunkloading, elytra deployment)
I did not use the optimize world option before playing.

boq

Ok, so let's try to unwind this:

  • Initial issue matches something we fixed few snapshots ago

  • Most recent snapshot is probably MC-134762, this may be fixed in next snapshot, but we will observe crash logs for some time before closing

  • Attached world is bit of a lost case, since it seems to be already corrupted - some chests have hopper data (like one at x:-281,y:30,z:-1233). In 1.12, they won't clicked when opened in survival and creative and open hopper menu in spectator. I suggest manually breaking and replacing those chests before importing. Anyway, whatever caused that is not part of this issue, since world was already corrupted in 1.12.1.

hoyskedotte

Yes it is getting better. I attached a new crashlog made in 1.14pre1.
Note that it crashes once and then that area is good. (may crash in other areas)

boq

As said, seems like it morphed into MC-134762 duplicate, I don't see point in keeping this open.

hoyskedotte

boq

Confirmed

Crash

Minecraft 1.13.2, Minecraft 18w43c, Minecraft 18w49a, Minecraft 19w08b, Minecraft 19w09a, Minecraft 19w11a, Minecraft 19w11b

Minecraft 1.14.1

Retrieved