William Sandey

Confirmed. Happens when placing last item from stack or when tool breaks (happened for me with stone ax).

I have "max-tick-time" set to 1920000 and still getting the crash. How high is it supposed to be to stop the crashing from occurring?

Getting a server crash also since upgrading to 14w31a this morning (attached crash report)

Slackware64 14.0
Java 1.8.0_05

My server crashed with a new world after about 30 to 45 minutes of having 5 players on it. After that crash, it was crashing about every minute.

My exiting server world I had since the snapshots for 1.7 started crashed in less a minute. I renamed the \world folder and started with a fresh map. ran fine for about 30 to 45 minutes (didn't time it), then it started crashing about every minute. I finally just restore my old map and went back to 27b for now.

Also note that the server does run fine, and players can log in and play on the server. It's only the console that is messed up.

Same here.

Slackware64 14.0
Java 8u5

Not a dupe. New issue. Console was working fine on 14w26a/b/c, but on 14w27a/b, it's useless. Screenshot of console for 14w27b on Linux server attached. Server is Slackware64 14.0 running Java 8u5.

This doesn't sound the same as the problem I had reported under MC-51144. I had the banned-players.json and ops.json wiped out after upgrading to 14w11b (don't use a whitelist, so I can't confirm if anything happened with that). These files were originally converted on my server with 14w10a.

The workaround for my problem was to stop the server, remove the banned-players.json and ops.json, rename the banned-players.txt.converted and ops.txt.converted to remove the .converted from the file name, and start the server. It correctly converted from the old format to the new format.

If you have to scroll to see all the items, the flickering is not there. So you can either add enough dummy entries or adjust the size of the windows so you have the scroll bar to make the flickering stop.

I've been getting a very similar error on my Linux server running 14w07a snapshot. Didn't get error in earlier snapshots. I attached my crash report as "crash-2014-02-16_22.11.18-server.txt"

I don't know if this helps for anyone else, but it did for me. I run my own server out of my home, and my router allows me to prioritize computers. I had my server in there to prioritize higher than other computer/devices, and was getting the error. I removed it from the high priority and made it normal priority, and I'm no longer getting kicked out with this error.

Just thought I would pass it along in case it might help anyone else out.

I'm still getting this error when I connect to my server. It's not a bad/slow Internet connection. I'm using the internal IP address of the server to connect over a 100Mbs Ethernet connection. Everything worked fine until 13w41a, and it has not worked since.

I'm getting the same error in the 1.7 Pre-Release. I haven't been able to play any of the last few snapshots in multiplayer because of this problem. I get in, I can play for a couple minutes, then get kicked. Come back in, and I need to figure out where I am since I'm not where I was when I got kicked. By the time I figure out where I am and where I need to go, I get kicked again.

You keep marking it "Resolved", but the problem is not fixed. Can you please fix this problem so it doesn't keep happening?

I'm getting the same error in the 1.7 Pre-Release. I haven't been able to play any of the last few snapshots in multiplayer because of this problem. I get in, I can play for a couple minutes, then get kicked. Come back in, and I need to figure out where I am since I'm not where I was when I got kicked. By the time I figure out where I am and where I need to go, I get kicked again.

You keep marking it "Resolved", but the problem is not fixed. Can you please fix this problem so it doesn't keep hjappening?

"EDIT: As seen on this post, it generally happens for people with worse connections, though I never got this error in previous versions."

No, this is not correct. I'm running my server at home, and my PC I play the client is connected via 100Mbs Ethernet, not over the Internet. And I get this error often.

I found that if stuck logging in, cancel, go to the main menu, and come back in helps.

I'm getting this with 13w42a, even though the changelog claims that it was fixed. I've attached my server log in case that helps. It shows several people getting kicked off today.

Server log file showing several players kicked off server at same time (at 16:31:22 on attached log file)

I searched for "1.6 reports 1.3", and got zero returns. Is there a more specific search terms I should have used?