Tried to read NBT tag that was too big
jannis3005 opened this issue ยท 2 comments
Describe the bug
It sometimes happens that when flying/walking around a player get's kicked with the message: "Internal Exception io.netty.handler.codec.DecoverException: java.lang.RuntimeException: Tried to read NBT tag that was too big: tried to allocate 2097153bytes where max allowed: 2097152" <- Only solution to "fix" a player and to allow him to play again is to teleport him somewhere else while joining and then letting him join again.
To Reproduce
- fly / wak around the server
- get kicked at random locations (though those locations seem to be constant for some time and sometimes change)
Expected behavior
Players should not get kicked and should not be prevented from joining
Screenshots / Scripts / Logs
There's nothing in the server log, it only shows "[10:49:53] [Server thread/INFO] [minecraft/ServerGamePacketListenerImpl]: X lost connection: Disconnected" There also seems to be nothing in the client log that's seems to be related to this.
The chunk that causes the crash has a block with too much NBT data. This is usually caused by a bunch of apotheosis spawners in someones storage system.
If you load the world in single player, pull the spawners out into something like normal/iron chests, then copy back the world files back to the server, you can recover.
The other alternative is to nuke the chunk that is causing the issue.
