Affects Version/s: Minecraft 1.7.9, Minecraft 14w25b, Minecraft 1.8-pre1, Minecraft 1.8, Minecraft 1.8.1-pre2, Minecraft 1.8.1-pre5, Minecraft 1.8.1, Minecraft 1.8.3, Minecraft 1.12, Minecraft 1.12.1 Pre-Release 1, Minecraft 1.12.1, Minecraft 1.12.2 Pre-Release 1, Minecraft 1.12.2 Pre-Release 2, Minecraft 1.12.2, Minecraft 17w43a, Minecraft 17w43b, Minecraft 17w45b, Minecraft 17w46a, Minecraft 17w48a, Minecraft 17w49a, Minecraft 17w50a, Minecraft 18w01a, Minecraft 18w02a, Minecraft 18w03b, Minecraft 18w06a, Minecraft 18w07b, Minecraft 18w07c, Minecraft 18w08b, Minecraft 18w09a, Minecraft 18w10c, Minecraft 18w10d, Minecraft 18w11a, Minecraft 18w20c, Minecraft 18w22c, Minecraft 1.13-pre1, Minecraft 1.13-pre2, Minecraft 1.13-pre3, Minecraft 1.13-pre4, Minecraft 1.13-pre9, Minecraft 1.13, Minecraft 18w31a, Minecraft 1.13.1-pre1, Minecraft 1.13.1-pre2, Minecraft 1.13.1
Fix Version/s: 1.15.2
This bug occurs when the attribute generic.followRange is set higher than a specific threshold. I already got this bug to work with 2048, 1000, 500 and 250 – it may be possible to reproduce it with lower/higher values too, though.
Basically, as soon as an entity with a "broken follow range" is spawned and finds an entity within that follow range (even if that entity is the player itself), the game will freeze, internally. This means that I can actually move and destroy/place blocks but cannot interact with entities or tile entities. Also, I cannot use items or commands and experience huge lag spikes.
As soon as I try to exit the world (any method seems to trigger this, even if I try to cause a debug crash by pressing F3 + C for 10 seconds) the game freezes completely. After the game window finally closes down, the launcher just shows me a message which tells me that the game has crashed, but no crash report is generated, unfortunately.
It seems like this can be reproduced with every mob which targets a specific entity or block in a specific occasion. This therefore also happens when punching passive mobs with the Panic AI enabled as this will cause the mob to target a random block within its follow range. However, the easiest way to reproduce this is to spawn a zombie with a villager next to it since this will definitely trigger the bug.
I used 2048 as the follow range because it is the max value which can be used according to the wiki, even though I've been able to spawn mobs with higher values, too. (These also triggered the bug)
What's really interesting about this is that I've never been able to render my test world corrupted when I reproduced this bug. When I re-join the test world after the crash, the spawned entity is gone and it's just like nothing ever happened. That's actually contrary to what the previous reporter said. They stated that the mob remained in their world and they couldn't re-join the world because it instantly crashed their client.
The attached crash reports were posted by the previous reporter. I can't get the game to crash like this anymore for some reason. I also can't get the game to output a crash report in earlier versions (such as 1.7.9).