A wandering trader spawned near me, I went over to him to check out the trades, but I didn't have any emeralds on me. So I went through the nether back to my home base to get emeralds, and when I came back, the game crashed a few seconds after coming out of the nether portal. I tried to load the world again and it crashed again. It seems I cannot play anymore.
19w05a\: [^crash-2019-01-30_20.16.41-server.txt]
---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.
Time: 1/30/19 8:16 PM
Description: Ticking entity
java.lang.NullPointerException: Ticking entity
at aho.a(SourceFile:1008)
at aho.dq(SourceFile:997)
at ahu.dq(SourceFile:70)
at aho.h(SourceFile:287)
at ank.h(SourceFile:588)
at ans.h(SourceFile:72)
at bcq.a(SourceFile:963)
at ur.a(SourceFile:365)
at bcq.f(SourceFile:943)
at bcq.k_(SourceFile:825)
at ur.k_(SourceFile:281)
at net.minecraft.server.MinecraftServer.b(SourceFile:865)
at tt.b(SourceFile:342)
at net.minecraft.server.MinecraftServer.a(SourceFile:796)
at net.minecraft.server.MinecraftServer.run(SourceFile:664)
at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Thread: Server thread
Stacktrace:
at aho.a(SourceFile:1008)
at aho.dq(SourceFile:997)
at ahu.dq(SourceFile:70)
at aho.h(SourceFile:287)
at ank.h(SourceFile:588)
at ans.h(SourceFile:72)
at bcq.a(SourceFile:963)
at ur.a(SourceFile:365)
at bcq.f(SourceFile:943)
-- Entity being ticked --
Details:
Entity Type: minecraft:trader_llama (ans)
Entity ID: 563
Entity Name: Trader Llama
Entity's Exact location: -712.49, 96.00, -308.50
Entity's Block location: World: (-713,96,-309), Chunk: (at 7,6,11 in -45,-20; contains blocks -720,0,-320 to -705,255,-305), Region: (-2,-1; contains chunks -64,-32 to -33,-1, blocks -1024,0,-512 to -513,255,-1)
Entity's Momentum: 0.00, -0.08, 0.00
Entity's Passengers: []
Entity's Vehicle: ~~ERROR~~ NullPointerException: null
Stacktrace:
at bcq.k_(SourceFile:825)
at ur.k_(SourceFile:281)
-- Affected level --
Details:
Level name: world
All players: 1 total; [ut['davidpyrzqxgl'/138, l='world', x=-863.98, y=69.00, z=-389.31]]
Chunk stats: ServerChunkCache: 4054
Level seed: 3315522725347464634
Level generator: ID 00 - default, ver 1. Features enabled: true
Level generator options: {}
Level spawn location: World: (-131,63,-121), Chunk: (at 13,3,7 in -9,-8; contains blocks -144,0,-128 to -129,255,-113), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 6632340 game time, 8019596 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 62991 (now: false), thunder time: 85431 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.b(SourceFile:865)
at tt.b(SourceFile:342)
at net.minecraft.server.MinecraftServer.a(SourceFile:796)
at net.minecraft.server.MinecraftServer.run(SourceFile:664)
at java.lang.Thread.run(Thread.java:745)
-- System Details --
Details:
Minecraft Version: 19w05a
Operating System: Linux (amd64) version 3.16.0-6-amd64
Java Version: 1.8.0_40, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 461679088 bytes (440 MB) / 1816133632 bytes (1732 MB) up to 5727322112 bytes (5462 MB)
JVM Flags: 5 total; -XX:MaxGCPauseMillis=100 -XX:+PrintGC -Xmx6G -Xmn2G -XX:+UseLargePages
Player Count: 1 / 20; [ut['davidpyrzqxgl'/138, l='world', x=-863.98, y=69.00, z=-389.31]]
Data Packs: vanilla
Is Modded: Unknown (can't tell)
Type: Dedicated Server (map_server.txt)
Related issues
is duplicated by
Attachments
Comments


We've seen the same thing here. The second attachment (20.16.41) is ours.
In our case, the clients were Windows and the server was Linux; server JVM is Oracle HotSpot, v1.8.0 u40.
In our case, the server crashed again after being restarted, as soon as a player joined the server, with essentially the same crash.

When trying again to load the world, it did not crash.

It seems that the crashing ceases with a second reload.
So:
Exit nether → Crash.
Reopen → Crash.
Reopen → OK.
This exception is also happening with sheeps, but is not related to entering/leaving nether, as described in duplicated [MC-143656].
Both crashes, with trader llamas and my sheep, have implied using a leash on mobs.

I have a single-player world I can no longer play because it crashes with this every time I load it. I'll try to run it on a server jar and see if I can kill the llamas/trader that were on my hillside. I'll add my crash log. I can upload the world if you need it.
EDIT: I was able to play right away when switching to a server .jar. However, today I started having this crash with even that on 19w06a. I know there is a trader in the area where I'm trying to zone in. I'll add the new crash report. UPDATE: After a few tries, I was able to zone in. I'm going to actively kill all traders/llamas now to see if that helps.
[MC-143797] duplicates this with a horse.

I have been having the same problem, but I am not sure which entities are causing the issue. Should I kill them all before playing? Or as Bob said, I can switch to a .jar world. How do I do that? I am on 19w07.
@unknown Look into your crash report to see which entity is causing the issues and what are their coordinates.

@Johnibur But the issue is, even with the coordinates, you can't edit the region file. None of the editors are updated for 1.14 yet and I can't find any that work. I also can't use the /kill method because the server crashes before commands are processed as the entity is in the spawn chunks.

@Noelle Leslie I think he just meant using a server.jar instead of loading it in single player? I'm not sure though, it was worded a little funny.
@unknown I use NBTExplorer for region files editing. You can also hard remove any entity by editing them directly in region files if you can't kill them in-game.

Still exists in 08a

FWIW I've never had this error before in any 1.14 snapshot until w08. Not sure why now and not before.
Entity Type: minecraft:horse (anx)
Entity ID: 167
Entity Name: Horse
(I was also promised a teddy bear which I never got)
Fixd typo

Got this for the first time today in 08a.
[media]
Having this issue in 19w08b as well.
[media]
I did the same thing. I had a dialog with a trader (did not buy anything), went to nether. When I came back game crashes.
[media]
*+Getting the same thing as of now (WORKAROUND AT THE BOTTOM)
+*
Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.
Time: 2/22/19 1:29 PM
Description: Ticking entity
java.lang.NullPointerException: Ticking entity
at ahw.a(SourceFile:1049)
at ahw.dD(SourceFile:1038)
at aic.dD(SourceFile:35)
at ahw.h(SourceFile:289)
at anw.h(SourceFile:573)
at aod.h(SourceFile:83)
at uv.a(SourceFile:565)
at uv$$Lambda$2520/222230043.accept(Unknown Source)
at bdf.a(SourceFile:683)
at uv.a(SourceFile:368)
at net.minecraft.server.MinecraftServer.b(SourceFile:837)
at net.minecraft.server.MinecraftServer.a(SourceFile:776)
at dtd.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:634)
at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
– Head –
Thread: Server thread
Stacktrace:
at ahw.a(SourceFile:1049)
at ahw.dD(SourceFile:1038)
at aic.dD(SourceFile:35)
at ahw.h(SourceFile:289)
at anw.h(SourceFile:573)
at aod.h(SourceFile:83)
at uv.a(SourceFile:565)
at uv$$Lambda$2520/222230043.accept(Unknown Source)
– Entity being ticked –
Details:
Entity Type: minecraft:trader_llama (aod)
Entity ID: 316
Entity Name: Trader Llama
Entity's Exact location: 564.36, 68.00, -6432.56
Entity's Block location: World: (564,68,-6433), Chunk: (at 4,4,15 in 35,-403; contains blocks 560,0,-6448 to 575,255,-6433), Region: (1,-13; contains chunks 32,-416 to 63,-385, blocks 512,0,-6656 to 1023,255,-6145)
Entity's Momentum: 0.00, -0.08, 0.00
Entity's Passengers: []
Entity's Vehicle: ~ERROR~ NullPointerException: null
Stacktrace:
at bdf.a(SourceFile:683)
at uv.a(SourceFile:368)
– Affected level –
Details:
Level name: To the End
All players: 1 total; [uw['money6543'/147, l='To the End', x=514.93, y=66.00, z=-6449.40]]
Chunk stats: ServerChunkCache: 4578
Level seed: -7454342621266938831
Level generator: ID 02 - largeBiomes, ver 0. Features enabled: true
Level generator options: {}
Level spawn location: World: (0,64,0), Chunk: (at 0,4,0 in 0,0; contains blocks 0,0,0 to 15,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 544251 game time, 806245 day time
Level dimension: 0
Level storage version: 0x04ABD - Anvil
Level weather: Rain time: 70719 (now: false), thunder time: 48731 (now: false)
Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
at net.minecraft.server.MinecraftServer.b(SourceFile:837)
at net.minecraft.server.MinecraftServer.a(SourceFile:776)
at dtd.a(SourceFile:128)
at net.minecraft.server.MinecraftServer.run(SourceFile:634)
at java.lang.Thread.run(Thread.java:745)
– System Details –
Details:
Minecraft Version: 19w08b
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_51, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 2107096496 bytes (2009 MB) / 3288334336 bytes (3136 MB) up to 4294967296 bytes (4096 MB)
JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx4G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M
Player Count: 1 / 8; [uw['money6543'/147, l='To the End', x=514.93, y=66.00, z=-6449.40]]
Data Packs: vanilla
Type: Integrated Server (map_client.txt)
Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
TEMPORARY FIX
I fixed my issue by using the NBT Editor, going to the Entity's exact location, and deleting the entity straight from there. Now my world is working again!

Same crash but with donkey.
Maybe it has something to do with entitys dissappearing and reappearing. Before the crash trader, traderllama, villagers and said donkey did randomly disappear (when going away and back they did not load) even standing right next to where they should be and trying to teleport them to me did not find them. Reloading the world did fix it most times but doesnt fix the crash.

I found a better fix for me: use NBT Editor to set "Leashed" to 0 .
I got five crashs for my five leashed animals and everytime "unleashed" one of them with help of the crash report to find it. So after starting minecraft five more times it now works. but still some Mobs dont load. for the time being i will try using boats instead of leashes.

This bug appears at every world load when the trader is around. I had this problem returning from neather, dying and loggin in and out of the game.
Really a big problem. Should be fixed as soon as possible.

Got the same bug, but with a leashed donkey. First it got invisible, and the leash disappeared too. Then, I continued to play normally and a zombie killed me near the invisible donkey, and it crashes my game whenever I enter the game. Will try to use a editor to remove it. By the way, it's on 19w08b.

Not sure if it was related at all, but I was building a skeleton farm and the hoppers where not collecting things at the killing spot. I couldn't for the life of me figure out why, so I tried restarting the game, but then my world would just crash upon loading, and I get this error. I could here hear the Llama trader just above me before I restarted. I've submitted my crash report with the others here.
Edit: After doing a bit more bug report hunting it looks like I have 2 separate issues going on. My hopper issue seems to be the same as MC-144603, and then this Ticking entity issue.

I have this same issue and have downlaoded NBT explorer/editor how do I know which file in the regions folder i need to open and how to edit it??
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– Head --Thread: Server threadStacktrace: at ahw.a(SourceFile:1049) at ahw.dD(SourceFile:1038) at aic.dD(SourceFile:35) at ahw.h(SourceFile:289) at anw.h(SourceFile:573) at aod.h(SourceFile:83) at uv.a(SourceFile:565) at uv$$Lambda$2606/1575331126.accept(Unknown Source)
– Entity being ticked --Details: Entity Type: minecraft:trader_llama (aod) Entity ID: 839 Entity Name: Trader Llama Entity's Exact location: 920.55, 177.50, 614.56 Entity's Block location: World: (920,177,614), Chunk: (at 8,11,6 in 57,38; contains blocks 912,0,608 to 927,255,623), Region: (1,1; contains chunks 32,32 to 63,63, blocks 512,0,512 to 1023,255,1023

The same "ticking entity" Error has been happening for me on my server.
[media]

Issue is not exclusive to trader llama, appears to be an issue with all ride-able entities. Have confirmed the same issue with trader llamas, as well as horses and donkeys. Attached are relevant crash reports. At a guess, it's a bug in how riders are handled.
[media][media][media]
How do you fix this?

I managed to temporarily "fix" the trader llama part by loading up a version before TLs were added (19w04b), going into the TL chunk and then loading it up again in 19w08b. There werent any "physical" additions since then apart from foxes and leather horse armor so your saves should probably be fine, still reccomend a backup. Also doesnt prevent more WTs with TLs from spawning.
@unknown If you don't know what to do, I strongly recommend to backup you world before doing any change an NBT editor. Looking at your crash report, it says is in chunk 57,38, which means you have to edit region number 1,1 (a region is a 32x32 chunks area and we start counting at 0). Open it in NBTEditor, search for chunk number 57,38, expand the view then search for entities tag, and when you have found the entity with id "trader_llama", remove all of its entries.

@Dish_Honored Thanks, I used your temporary solution and my world is at least playable now.

Same thing happened to me, I start the world and it instantly crashed due to the ticking entity, not sure which one. I have 2 horses but I don't believe any WT were around me last time I logged in.

I am experiencing this crash too. That, combined with MC-143420, make it a nightmare to play on these snapshots. No way to prevent them from spawning, and the game crashes when they appear on screen.

My horse spawned out of existence last time I opened the world, and the game seemed like it was freezing, I noticed it in the smoker, and I logged back in this morning and saw my invisible horse spawn back in the distance before it crashed my game. Keeps crashing my game ever since.

I removed all entities with the /kill command and that didn't even work. The mobs/animals that were ticking were respawning even though I saved after I removed them. So yes, I can confirm this happens to me too. Very annoying.

Same issue here, also tried to kill the trader_llama with the kill command but doesn't work. Can't open my world now because I crash instantly

Also experiencing this issue. When one entity stops giving the bug for whatever error, it switches to another one.
For example, I tamed a cat which seemed to start this whole ordeal. Then it was a polar bear in my base.

Same issue for me too....

:flag_on: GOT A TEMPORARY FIX!!! Set video settings to render distance 2 chunks before going in the save and load the save.

Thanks Kable, that temporary fix worked for me

I also have the same issue, in 19w08b:
---- Minecraft Crash Report -------- Minecraft Crash Report ----// Surprise! Haha. Well, this is awkward.
Time: 27.02.19 11:25Description: Ticking entity
java.lang.NullPointerException: Ticking entity at ahw.a(SourceFile:1049) at ahw.dD(SourceFile:1038) at aic.dD(SourceFile:35) at ahw.h(SourceFile:289) at anw.h(SourceFile:573) at aod.h(SourceFile:83) at uv.a(SourceFile:565) at uv$$Lambda$2462/368255940.accept(Unknown Source) at bdf.a(SourceFile:683) at uv.a(SourceFile:368) at net.minecraft.server.MinecraftServer.b(SourceFile:837) at net.minecraft.server.MinecraftServer.a(SourceFile:776) at dtd.a(SourceFile:128) at net.minecraft.server.MinecraftServer.run(SourceFile:634) at java.lang.Thread.run(Thread.java:745)A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Server threadStacktrace: at ahw.a(SourceFile:1049) at ahw.dD(SourceFile:1038) at aic.dD(SourceFile:35) at ahw.h(SourceFile:289) at anw.h(SourceFile:573) at aod.h(SourceFile:83) at uv.a(SourceFile:565) at uv$$Lambda$2462/368255940.accept(Unknown Source)
-- Entity being ticked --Details: Entity Type: minecraft:trader_llama (aod) Entity ID: 112 Entity Name: Handelslama Entity's Exact location: -5481.15, 64.36, -7586.80 Entity's Block location: World: (-5482,64,-7587), Chunk: (at 6,4,13 in -343,-475; contains blocks -5488,0,-7600 to -5473,255,-7585), Region: (-11,-15; contains chunks -352,-480 to -321,-449, blocks -5632,0,-7680 to -5121,255,-7169) Entity's Momentum: 0.17, 0.28, -2.24 Entity's Passengers: [] Entity's Vehicle: ~~ERROR~~ NullPointerException: nullStacktrace: at bdf.a(SourceFile:683) at uv.a(SourceFile:368)
-- Affected level --Details: Level name: Ny Verden All players: 1 total; [uw['eirikh1996'/108, l='Ny Verden', x=-5485.50, y=68.10, z=-7568.50]] Chunk stats: ServerChunkCache: 2981 Level seed: -5128221254728419811 Level generator: ID 00 - default, ver 1. Features enabled: true Level generator options: {} Level spawn location: World: (-176,68,-16), Chunk: (at 0,4,0 in -11,-1; contains blocks -176,0,-16 to -161,255,-1), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1) Level time: 907518 game time, 935474 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 141776 (now: false), thunder time: 92970 (now: false) Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: trueStacktrace: at net.minecraft.server.MinecraftServer.b(SourceFile:837) at net.minecraft.server.MinecraftServer.a(SourceFile:776) at dtd.a(SourceFile:128) at net.minecraft.server.MinecraftServer.run(SourceFile:634) at java.lang.Thread.run(Thread.java:745)
-- System Details --Details: Minecraft Version: 19w08b Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1411285088 bytes (1345 MB) / 3087007744 bytes (2944 MB) up to 3221225472 bytes (3072 MB) JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx3G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Player Count: 1 / 8; [uw['eirikh1996'/108, l='Ny Verden', x=-5485.50, y=68.10, z=-7568.50]] Data Packs: vanilla Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
Unfortunately @Kalbe it didn't work for me as the ticking entity was within range

Resolved. Awesome. Hopefully next snapshot.

Not resolved. Happened in 19w12a. Won't let me play.
Minecraft Crash Report -------- Minecraft Crash Report ----// Oh - I know what I did wrong!
Time: 3/20/19 12:34 PMDescription: Ticking block entity
java.lang.NullPointerException: Ticking block entity at ev.<init>(SourceFile:52) at bso.i(SourceFile:194) at bso.g(SourceFile:104) at bgf.K(SourceFile:620) at vd.a(SourceFile:401) at net.minecraft.server.MinecraftServer.b(SourceFile:816) at net.minecraft.server.MinecraftServer.a(SourceFile:755) at dwc.a(SourceFile:128) at net.minecraft.server.MinecraftServer.run(SourceFile:630) at java.lang.Thread.run(Thread.java:745)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– Head --Thread: Server threadStacktrace: at ev.<init>(SourceFile:52) at bso.i(SourceFile:194) at bso.g(SourceFile:104)
– Block entity being ticked --Details: Name: minecraft:conduit // bso Block: Block{minecraft:conduit}[waterlogged=true] Block location: World: (60,69,-200), Chunk: (at 12,4,8 in 3,-13; contains blocks 48,0,-208 to 63,255,-193), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1) Block: Block{minecraft:conduit}[waterlogged=true] Block location: World: (60,69,-200), Chunk: (at 12,4,8 in 3,-13; contains blocks 48,0,-208 to 63,255,-193), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1)Stacktrace: at bgf.K(SourceFile:620) at vd.a(SourceFile:401)
– Affected level --Details: Level name: DanTDM's New Lab All players: 0 total; [] Chunk stats: ServerChunkCache: 2025 Level seed: -4794258602603451750 Level generator: ID 01 - flat, ver 0. Features enabled: false Level generator options: {biome:"minecraft:plains",layers:[{block:"minecraft:bedrock",height:1},{block:"minecraft:stone",height:59},{block:"minecraft:dirt",height:3},{block:"minecraft:grass_block",height:1}],structures:{biome_8:{},village:{}}} Level spawn location: World: (83,4,-117), Chunk: (at 3,0,11 in 5,-8; contains blocks 80,0,-128 to 95,255,-113), Region: (0,-1; contains chunks 0,-32 to 31,-1, blocks 0,0,-512 to 511,255,-1) Level time: 13284120 game time, 2030454 day time Level dimension: 0 Level storage version: 0x04ABD - Anvil Level weather: Rain time: 1 (now: false), thunder time: 1 (now: false) Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: trueStacktrace: at net.minecraft.server.MinecraftServer.b(SourceFile:816) at net.minecraft.server.MinecraftServer.a(SourceFile:755) at dwc.a(SourceFile:128) at net.minecraft.server.MinecraftServer.run(SourceFile:630) at java.lang.Thread.run(Thread.java:745)
– System Details --Details: Minecraft Version: 19w12a Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1414646656 bytes (1349 MB) / 2147483648 bytes (2048 MB) up to 2147483648 bytes (2048 MB) JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Player Count: 0 / 8; [] Data Packs: vanilla Type: Integrated Server (map_client.txt) Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.
@unknown, that crash is a different issue. The stack trace is not the same as this one and the entity being tick in your issue is minecraft:conduit at 60 69 -200.
Edit: Someone just made a bug report on it, see MC-146246.

This issue (or something related) seems to be back with 1.14.1-pre1.
1.14.1-pre1 appears to try and expire llamas. I visited a chunk created in 1.14 with a villager trader and some trader llamas. The server immediately crashes with:
– Entity being ticked –
Details:
Entity Type: minecraft:villager (avl)
Entity ID: 14986
Entity Name: Villager
Entity's Exact location: 346.41, 64.00, 1347.98
Entity's Block location: World: (346,64,1347), Chunk: (at 10,4,3 in 21,84; contains blocks 336,0,1344 to 351,255,1359), Region: (0,2; contains chunks 0,64 to 31,95, blocks 0,0,1024 to 511,255,1535)
Entity's Momentum: 0.00, -0.08, 0.00
Entity's Passengers: []
Entity's Vehicle: ~ERROR~ NullPointerException: null
Stacktrace:
at bhi.a(SourceFile:676)
at vg.a(SourceFile:383)
I have attached a full copy of crash-2019-05-08_10.07.13-server
[media]