mojira.dev
MC-127242

Drowned causes crashes (ticking entity)

The bug

Drowned causes the game to randomly crash.

A code analysis by @unknown can be found in this comment.

Linked issues

MC-127243 Drowned causes frequent and random crashes Resolved MC-127306 Entities causing ticking entity crash Resolved MC-127328 Crash after sleeping in bed Resolved MC-127390 [18w11a] minecraft:drowned Ticking entity crashing server Resolved MC-127412 18w11a bug Resolved

Attachments

Comments 21

Affects 18w11a.

This crashed our server last night with the exact same crash report. We solved it by issuing the kill command, but are of course hoping the underlying bug will be resolved.

This happened to me also, I am unable to get into my world because it crashes as soon as I get into it. Deleting drowned with an NBT editor allows me to get back in, but I am right next to a zombie spawner so within seconds it crashes again.

I also have this issue on my linux multiplayer server.
For now, I did /kill @e[type=drowned] and /gamerule doMobSpawn false so we can at least play without mobs until a fix.

Seth Robichaud

temporary fix without killing/disabling mobs is to switch back to 18w10d until this is resolved. Worked for me.

11 more comments

Hi Team,

I have had this occur now twice, in two different worlds both in survival mode. One I created and have played many snapshots on and the other was a demo world I created long ago that I decided to start playing when the other became corrupted. Due to this specific bug along with performance issues with this release, I will likely choose to wait until GA as this is simply unacceptable that this is still open in JIRA and hasn't moved at all. I'm including two log files from each instance for static testing. Each are on the same test host with no changes from baseline. While not exactly a bug, I may need to file one as performance on macOS 10.12.6 has really been impacted with the additions added in this update. In fact, I had to totally disable any 32 or 64 resource pack and even the low end shaders as well. What is strange is that the FPS in vanilla was still the same but performance seems to be related to large chunks that appear to be attempting to render but do not. This is on macOS 10.12.6, (any beta snapshot so far, including 18w11a), Core i7 2.3Ghz, 16GB DDR3, Intel HD4000. Frankly, my Lenovo Ultrabook does not far much better with Windows 10 1701.

This bug is really difficult to address if anyone expects some serious bug testing from crowdsourcing QA. We have to be able to play the snapshots to report the bugs. We cannot do that at the moment once this is encountered. On a final note, I was at MineCon Earth with my son at Microsoft and I find it disconcerting that these issues still persist and GA should be already a confirmed date. Please address these performance issues and review the logs to address this bizarre bug. Thank you.

[media][media]

There's no need to keep adding crash reports to this ticket. Thank you.

Confirmed with 18W14A

This bug is back with 19w13a or is related to this one

For me this happened after I put some villagers in boats, and an outside villager started to want to breed with one in the boat. The boat caused the ticking error.

I tried destroying the boats, but then the villagers started to also create the ticking error.

@unknown: Your issue is MC-146783.

campoy

[Mod] Neko

Agnes Larsson

Confirmed

Minecraft 18w11a, Minecraft 18w14a

Minecraft 18w14b

Retrieved