mojira.dev
MC-140880

Pillager riding ravager - Ravager dies - Fatal Ticking Entity

The bug

Raid involving pillager riding ravager, ravager ran under village roof overhang, causing repeated injury to pillager, player killed ravager, pillager appeared stuck within roof block, Fatal Ticking Entity ensued.  

Crash report

19w09a\: [^crash-2019-03-03_22.12.33-server.txt]

Description: Ticking entity

java.lang.NullPointerException: Ticking entity
	at ahm.c(SourceFile:1205)
	at ate$a.e(SourceFile:262)
	at ajv.a(SourceFile:129)
	at ahw.cV(SourceFile:612)
	at ahv.k(SourceFile:2169)
	at ahw.k(SourceFile:477)
	at aqn.k(SourceFile:33)
	at ate.k(SourceFile:73)
	at ahv.h(SourceFile:2018)
	at ahw.h(SourceFile:291)
	at aqn.h(SourceFile:45)
	at ahm.aL(SourceFile:1639)
	at ahv.aL(SourceFile:2308)
	at uv.a(SourceFile:595)
	at uv.a(SourceFile:573)
	at bdf.a(SourceFile:683)
	at uv.a(SourceFile:368)
	at net.minecraft.server.MinecraftServer.b(SourceFile:837)
	at tw.b(SourceFile:342)
	at net.minecraft.server.MinecraftServer.a(SourceFile:776)
	at net.minecraft.server.MinecraftServer.run(SourceFile:634)
	at java.lang.Thread.run(Unknown Source)

Linked issues

Attachments

Comments 8

Oddly enough, I got the exact same crash, but with a witch.

I got the same except my crash was different, but i believe related

[media]

this was in 18w50a

I'm unable to play, as it crashes every time my world is loaded.

Having the same Problem!

 

 

The game crashed whilst ticking entity
Error: java.lang.NullPointerException: Ticking entity

The only way to start playing again is either del your player file or edit ya player file so your location when u spawn in is sufficiently far away that area is no longer loaded

This is happening with the new snapshot 19w03a.  I am unable to start my server due to a ticking Pillager entity.  Two Pillager Beasts with riders were being slowly killed by the berry bushes I have planted around the base (since we can't kill with bows with the current known arrows/tridents bug introduced in this snapshot).  From what I saw just before the disconnect (server crash), one of the Beasts was killed when this triggered.  The server shuts down with the same crash report every time ever since:

 


Minecraft Crash Report -------- Minecraft Crash Report ----// Daisy, daisy...
Time: 17/01/19 8:49 AMDescription: Ticking entity
java.lang.NullPointerException: Ticking entity at ahc.c(SourceFile:1251) at aso$a.e(SourceFile:262) at ajj.a(SourceFile:129) at ahm.cT(SourceFile:608) at ahl.k(SourceFile:2041) at ahm.k(SourceFile:473) at aqc.k(SourceFile:33) at aso.k(SourceFile:73) at ahl.h(SourceFile:1892) at ahm.h(SourceFile:284) at aqc.h(SourceFile:45) at bci.a(SourceFile:988) at ur.a(SourceFile:392) at bci.g(SourceFile:968) at bci.m_(SourceFile:850) at ur.m_(SourceFile:308) at net.minecraft.server.MinecraftServer.b(SourceFile:827) at ts.b(SourceFile:338) at net.minecraft.server.MinecraftServer.a(SourceFile:756) at net.minecraft.server.MinecraftServer.run(SourceFile:622) at java.lang.Thread.run(Unknown Source)

A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– Head --Thread: Server threadStacktrace: at ahc.c(SourceFile:1251) at aso$a.e(SourceFile:262) at ajj.a(SourceFile:129) at ahm.cT(SourceFile:608) at ahl.k(SourceFile:2041) at ahm.k(SourceFile:473) at aqc.k(SourceFile:33) at aso.k(SourceFile:73) at ahl.h(SourceFile:1892) at ahm.h(SourceFile:284) at aqc.h(SourceFile:45) at bci.a(SourceFile:988) at ur.a(SourceFile:392) at bci.g(SourceFile:968)
– Entity being ticked --Details: Entity Type: minecraft:pillager (aqg) Entity ID: 123 Entity Name: Pillager Entity's Exact location: 206.03, 73.20, 94.10 Entity's Block location: World: (206,73,94), Chunk: (at 14,4,14 in 12,5; contains blocks 192,0,80 to 207,255,95), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511) Entity's Momentum: 0.00, -0.08, 0.00 Entity's Passengers: [] Entity's Vehicle: ~ERROR~ NullPointerException: nullStacktrace: at bci.m_(SourceFile:850) at ur.m_(SourceFile:308)
– Affected level --Details: Level name: Terror World All players: 0 total; [] Chunk stats: ServerChunkCache: 2025 Level seed: -7784199051844829648 Level generator: ID 00 - default, ver 1. Features enabled: true Level generator options: {} Level spawn location: World: (240,66,130), Chunk: (at 0,4,2 in 15,8; contains blocks 240,0,128 to 255,255,143), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511) Level time: 21423131 game time, 23189257 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 155179 (now: false), thunder time: 40892 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: falseStacktrace: at net.minecraft.server.MinecraftServer.b(SourceFile:827) at ts.b(SourceFile:338) at net.minecraft.server.MinecraftServer.a(SourceFile:756) at net.minecraft.server.MinecraftServer.run(SourceFile:622) at java.lang.Thread.run(Unknown Source)
– System Details --Details: Minecraft Version: 19w03a Operating System: Windows 7 (amd64) version 6.1 Java Version: 1.8.0_191, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 322630840 bytes (307 MB) / 1123315712 bytes (1071 MB) up to 8572502016 bytes (8175 MB) JVM Flags: 6 total; -Xmx8G -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSIncrementalPacing -XX:ParallelGCThreads=2 -XX:+AggressiveOpts Player Count: 0 / 20; [] Data Packs: vanilla Is Modded: Unknown (can't tell) Type: Dedicated Server (map_server.txt)

I have fixed the issue myself using NBTExplorer.  Using the available crash report information I located the offending Pillager's tags and changed the OnGround value from 0 to 1.  It appears that having a value of 0 also assumes that there would be vehicle information and there wasn't.  By changing the value to 1 this bypassed the issue.

 

Now if I could just figure out the weird invisible entity issues that crop up in these snapshots.....  rolls eyes

In my crash report the affected entity is the ravager and not the rider, however the situation is very similar. During a raid I attacked a beast with my wolves, and suddenly the game crashed.

Entity Type: minecraft:ravager (aqt)

[media]

 

Jeff

(Unassigned)

Community Consensus

Crash, Mob behaviour

Minecraft 18w49a, Minecraft 19w02a, Minecraft 19w03a, Minecraft 19w08b, Minecraft 19w09a, Minecraft 19w11a, Minecraft 19w11b

Retrieved