mojira.dev
MC-139333

Crash occurs randomly during gameplay whilst loading NBT data

At some random point after starting Minecraft or opening the world, the game would crash within seconds and have random lag spikes before it does actually crash. This occurs normally when trying to load NBT data. Crash report data below:

[^crash-2018-11-13_17.56.26-server.txt]

Description: Loading NBT data

java.io.EOFException: Unexpected end of ZLIB input stream
	at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:240)
	at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
	at java.io.DataInputStream.readFully(DataInputStream.java:195)
	at java.io.DataInputStream.readUTF(DataInputStream.java:609)
	at java.io.DataInputStream.readUTF(DataInputStream.java:564)
	at ho.b(SourceFile:430)
	at ho.a(SourceFile:78)
	at hu.a(SourceFile:69)
	at ho.a(SourceFile:437)
	at ho.a(SourceFile:81)
	at ho.a(SourceFile:437)
	at ho.a(SourceFile:81)
	at hy.a(SourceFile:119)
	at hy.a(SourceFile:84)
	at hy.a(SourceFile:80)
	at bqh.a(SourceFile:103)
	at bqh.b(SourceFile:87)
	at bqh.a(SourceFile:137)
	at uc.d(SourceFile:430)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590)
	at java.util.ArrayList.forEach(ArrayList.java:1249)
	at uc.d(SourceFile:360)
	at uc.a(SourceFile:272)
	at bpn.a(SourceFile:14)
	at azy.a(SourceFile:1740)
	at azz.a(SourceFile:56)
	at akq.j(SourceFile:141)
	at akq.a(SourceFile:87)
	at aks.a(SourceFile:61)
	at ud.a(SourceFile:186)
	at net.minecraft.server.MinecraftServer.b(SourceFile:765)
	at net.minecraft.server.MinecraftServer.a(SourceFile:702)
	at dmf.a(SourceFile:128)
	at net.minecraft.server.MinecraftServer.run(SourceFile:568)
	at java.lang.Thread.run(Thread.java:745)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Thread: Server thread
Stacktrace:
	at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:240)
	at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
	at java.io.BufferedInputStream.read1(BufferedInputStream.java:284)
	at java.io.BufferedInputStream.read(BufferedInputStream.java:345)
	at java.io.DataInputStream.readFully(DataInputStream.java:195)
	at java.io.DataInputStream.readUTF(DataInputStream.java:609)
	at java.io.DataInputStream.readUTF(DataInputStream.java:564)
	at ho.b(SourceFile:430)
	at ho.a(SourceFile:78)
	at hu.a(SourceFile:69)

-- NBT Tag --
Details:
	Tag name: Sections
	Tag type: 9
Stacktrace:
	at ho.a(SourceFile:437)
	at ho.a(SourceFile:81)
	at ho.a(SourceFile:437)
	at ho.a(SourceFile:81)
	at hy.a(SourceFile:119)
	at hy.a(SourceFile:84)
	at hy.a(SourceFile:80)
	at bqh.a(SourceFile:103)
	at bqh.b(SourceFile:87)
	at bqh.a(SourceFile:137)
	at uc.d(SourceFile:430)
	at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590)
	at java.util.ArrayList.forEach(ArrayList.java:1249)
	at uc.d(SourceFile:360)
	at uc.a(SourceFile:272)
	at bpn.a(SourceFile:14)
	at azy.a(SourceFile:1740)
	at azz.a(SourceFile:56)
	at akq.j(SourceFile:141)
	at akq.a(SourceFile:87)

-- Entity being ticked --
Details:
	Entity Type: minecraft:sheep (alr)
	Entity ID: 318
	Entity Name: Sheep
	Entity's Exact location: -10.16, 63.00, 20.36
	Entity's Block location: World: (-11,63,20), Chunk: (at 5,3,4 in -1,1; contains blocks -16,0,16 to -1,255,31), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
	Entity's Momentum: 0.00, -0.08, 0.00
	Entity's Passengers: []
	Entity's Vehicle: ~~ERROR~~ NullPointerException: null
Stacktrace:
	at azy.n_(SourceFile:1029)
	at ud.n_(SourceFile:296)
	at net.minecraft.server.MinecraftServer.b(SourceFile:773)
	at net.minecraft.server.MinecraftServer.a(SourceFile:702)
	at dmf.a(SourceFile:128)
	at net.minecraft.server.MinecraftServer.run(SourceFile:568)
	at java.lang.Thread.run(Thread.java:745)

Linked issues

Attachments

Comments 2

Can you attach the world?

Yes, but the problem happens both in the world and on the title screen. It crashes regardless of activity on the world, and because the world cannot save when it crashes with NBT error, it rolls the data back to the way it was when it was actually saved.

Spencer Rushlow

(Unassigned)

Unconfirmed

Minecraft 18w45a

Retrieved