The bug
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.
How to reproduce
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.
/summon zombie ~ ~2 ~ {Attributes:[{Name:generic.followRange,Base:2048}]}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).
Linked issues
is duplicated by 13
Attachments
Comments 13
same java exception in report MC-75144, (java.lang.RuntimeException: Already decorating )
But not exact same issue, I was only drawing a map.
5 Reports attached on my issue.
affects also 1.8.1
Confirmed on Server 1.8.1.
The only way to reproduce is to run around in not yet generated area.
[20:24:23] [Server thread/ERROR]: Encountered an unexpected exception
u: Exception ticking world
at net.minecraft.server.MinecraftServer.A(SourceFile:604) ~[minecraft_server.1.8.1.jar:?]
at pp.A(SourceFile:299) ~[minecraft_server.1.8.1.jar:?]
at net.minecraft.server.MinecraftServer.z(SourceFile:532) ~[minecraft_server.1.8.1.jar:?]
at net.minecraft.server.MinecraftServer.run(SourceFile:448) [minecraft_server.1.8.1.jar:?]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_25]
Caused by: java.lang.RuntimeException: Already decorating
at arv.a(SourceFile:25) ~[minecraft_server.1.8.1.jar:?]
at arj.a(SourceFile:389) ~[minecraft_server.1.8.1.jar:?]
at asa.a(SourceFile:143) ~[minecraft_server.1.8.1.jar:?]
at bgt.a(SourceFile:472) ~[minecraft_server.1.8.1.jar:?]
at qt.a(SourceFile:174) ~[minecraft_server.1.8.1.jar:?]
at bff.a(SourceFile:872) ~[minecraft_server.1.8.1.jar:?]
at qt.c(SourceFile:104) ~[minecraft_server.1.8.1.jar:?]
at qt.d(SourceFile:116) ~[minecraft_server.1.8.1.jar:?]
at aqr.a(SourceFile:276) ~[minecraft_server.1.8.1.jar:?]
at qu.h(SourceFile:327) ~[minecraft_server.1.8.1.jar:?]
at qu.c(SourceFile:202) ~[minecraft_server.1.8.1.jar:?]
at net.minecraft.server.MinecraftServer.A(SourceFile:600) ~[minecraft_server.1.8.1.jar:?]
... 4 moreFunny this same thing happend to me Im playing minecraft then I spawn in a mob this command
/summon SnowMan ~0 ~1 ~0 {CustomName:Dr.Snow,CustomNameVisible:1,Attributes:[{Name:generic.maxHealth,Base:10},{Name:generic.movementSpeed,Base:0.4},{Name:generic.attackDamage,Base:1},{Name:generic.followRange,Base:999}]}I hit him a few times then my game crashes
I was able to break the command block and fix a few things I think whats going on is the block limit but not sure Im testing that right now!
Can confirm for MC 1.12.1, although it seems like the exact effects changed a bit. Also, this only seems happens in survival mode.
Since this ticket hasn't been updated for over a year, can a moderator please make me the reporter of the ticket so I can update it? Thanks!
I'm not entirely sure why, but it seems in 1.13pre-9, the game no longer crashes when clicking on "Save and quit to title" – instead it quits to the title screen and resets the world to a point in time where the zombie did not exist.
However, after repeatedly spawning the zombie, quitting to title screen, rejoining the world, and spawning the zombie again, the game eventually gets in a super unstable state and doesn't respond to user input anymore.
bemoty
I have a bunch of these type of crashes and it happens alot now since 1.9 on smp here is my crash reports