Matthew Hodson

It also effects zombies and skeletons, creepers and pigs (14w29b).
They move about 1/10th the speed they should have in water.
Its faster to build land bridges or manually push farmyard animals across water.
Wolves seem to not only suffer the slow movement but fail to teleport more oft than not.

Is it safe to revert a world from 14w07a to 14w05b do you think?

I am hoping this was fixed in 14w07a but it was not mentioned. Lost alot of things to this bug.

Also it doesn't appear to have anything to do with digging up, or even digging. Its just when any entity is created they appear to move further than previously and glitch into walls/ceilings/floors. Entities inside blocks naturally float upwards so a common experience when caving is to find entities on the surface or in higher caves

I had a few instances of "didn't I mine more diamond/gold than that?" and randomly finding block entities in caves around where I had been digging before realizing what was going on.
This has been happening quite a lot

Second dev console.
I've had less crashes since changing to 2Gig min-max java memory but that might be just random chance.

This time the fps seemed to be taking some hits shortly before the crash.
It crashed almost immediately after unpausing the game.
I had firefox open in the background playing a youtube vid, firefox didnt have to quit, though it usually does even it was pretty much doing nothing on a static web page.

Played for ~1 hour with no crash, then played for ~16 minutes and experienced the crash.
At the time of crash I was feeding animals, about 20 pigs, cows chickens and a few sheep in a 25x25 pen during day, no rain.
When minecraft crashed it also crashed my audioplayer (media monkey)

1. Will post full output asap.
2. MCL 131 is not similar at all
My last comment "Minecraft is unplayable" was technically hyperbole.
The game will crash after 2minutes, 10 minutes or 25 minutes of gameplay; my minecraft sessions almost always end with a crash making it too frustrating to play.

I had the default JVM arguments when this first happened with 1.6 (it has happened with older versions but I think 1.5.2 it didnt).
I changed to -Xincgc -Xms1G -Xmx3G and still had the same problem;
now I'm trying -Xincgc -Xms2G -Xmx2G
Maybe a static size will help. This is just a hunch that its java memory issues causing a delay in dealing with video drivers which then timeout.

Its really hard to diagnose since it can happen over and over every 2 or 3 mins, or not happen for half an hour or longer. It didnt happen just now for instance when I tried to get a console output.