[MC-91043] Packet 0/72 (ia) was larger than I expected, found 19 bytes extra whilst reading packet 72

When I connect to my multiplayer server, while the chunks are still loading I get the following IOException:

Packet 0/72 (ia) was larger than I expected, found 19 bytes extra whilst reading packet 72

Linked issues

is duplicated by 17

MC-91047 minecraft server keeps quitting me out Resolved

MC-91051 Error Message on server connect Resolved

MC-91069 Crash on server Resolved

MC-91070 Internal Exception, when joining server from earlier snapshot Resolved

MC-91077 Unable to connect to server with 15w43a Resolved

12 more links

Attachments

Comments 21

Aaron Eichhorst 2015-10-21T16:33:01Z

I'm experiencing the same issue. I was fine briefly while in the spawn chunk area, but I teleported away and this same error came up and repeats every time I log back in.

EDIT: After some more testing, I managed to stay logged in briefly in my spawn chunks, but the error occurred immediately whenever I tried to interact with a block/entity (e.g. opening a chest.)

jensz12 2015-10-21T16:39:15Z

I have the same issue

aiden shade hindley 2015-10-21T16:55:43Z

same

jensz12 2015-10-21T16:56:13Z

Its not only on Windows 10

jensz12 2015-10-21T16:58:15Z

Sceenshot of server log, when it happens

11 more comments

aiden shade hindley 2015-10-21T16:58:54Z

anybody have any ideas to work around it because i really wanted to play with some people and they cant wait to go on this snapshot

Maximilian Kennedy-Herron 2015-10-21T17:00:30Z

I can confirm the same issue for me and one other person on two separate servers from both pre- and post-43a. We're both running 64bit Win7 and the servers were running on my computer.

At a speculative glance, it appears to be related to client-side block placement as I can move around in areas that are already built before I start playing without issue. Placing blocks appears to cause the error invariably within a second as does being in an area where chunks haven't yet been generated. Using the server to place blocks (/setblock) does not appear to cause a disconnect while I am in the server. The server holds up fine and does not report any error.

jensz12 2015-10-21T17:00:52Z

Aiden
You will probably have to wait until Mojang fixes it, It will most likely not be today.

jensz12 2015-10-21T17:02:39Z

Maximillian, i cant do anything in a freshly created world on my server, so i doubt it

aiden shade hindley 2015-10-21T17:03:32Z

ok sorry thanks i can live with 15w42a

Maximilian Kennedy-Herron 2015-10-21T17:03:38Z

I edited my post to confirm what I meant, sorry.

To reiterate, generating the world appears to disconnect the client, as does the client placing blocks in an already fully generated area.

Nikita Andreev 2015-10-21T17:58:42Z

Same issue on OSX 10.10.
Server - Ubuntu 14.04

Richard Murray 2015-10-21T23:22:34Z

I'm having the same problem as well. I was trying to get my sister on my LAN world, but that failed. So I tried a server, and that failed also. I have x64 Windows 10 Education Edition, and Java 8, Update 65; If that helps.

Ben Freund 2015-10-21T23:37:03Z

Same issue here!

Andy (Romaq) Smith 2015-10-22T02:52:12Z

Rolling back to the last snapshot. 😞 Glad I made a backup!

Do I understand correctly the way this was "fixed" likely means a release 15w43b soon-ish?

Keith Elliott 2015-10-22T03:25:32Z

Had the same error. Also happened whenever a button was pressed.

Cameron Arnott 2015-10-22T08:12:14Z

I hope the fix gets released soon

Yann Davin 2015-10-22T11:27:59Z

Just quoting Dinnerbone's tweet :
"There'll be a 'b' snapshot today to fix multiplayer not working, some improvements to loot tables, and maybe some other sneaky things."

It looks like he was talking about this bug. Nice !

Lucas Sweat 2015-10-22T20:27:00Z

I am still having problem with this bug even with 15w43b. I'm not sure what's that about.

[Mod] redstonehelper 2015-10-22T20:28:08Z

@unknown: Is your server updated as well?

Lucas Sweat 2015-10-22T20:37:43Z

Oh, that was my problem. I though I had the latest server too. Sorry about that.