Crash while ticking barrel

Can confirm for 19w11a. When opening a barrel crashes Minecraft with the message: "The game crashed whilst ticking block entity || Error: java.lang.IllegalStateException: POI never registered at eu{x=-49, y=67, z=241}"

To add to it. Seems like it only affects barrels that was in the world already (in my case from earlier snapshots).

Edit: Forgot to mention that I am playing on snapsgot 19w11a

If I travel to a villlage, that I have visited earlier, and place down a barrel next to a "village generated" one, there are no problem at all opening the new barrel.
But, as soon as I try to open the "village generated", I got an crash with ticking entity. 

Description: Ticking block entity
java.lang.IllegalStateException: POI never registered at eu{x=286, y=74, z=1565}

If I do F3+I on both, I am getting the exact same result.

/setblock 288 74 1564 minecraft:barrel[facing=up,open=false]{Items:[]}
/setblock 286 74 1565 minecraft:barrel[facing=up,open=false]{Items:[]}

Still present in all Snapshots upto and including 11b

I have this issue with ticking a chest. Created the world in 19w09a and received the crash within the same version shortly after. The crash reoccurs also in later snapshots, making the world unplayable. 

Confirmed 19w11b

Crash after opening a barrel placed before updating to the snapshot.

Unable to open world after the crash, as it crashes again with the same error.

later noted this is related to MC-145868

---- Minecraft Crash Report ----
// Shall we play a game?

Time: 3/17/19 10:26 PM
Description: Ticking block entity

java.lang.IllegalStateException: POI never registered at eu\{x=187, y=73, z=41}
 at apa.a(SourceFile:72)
 at aoy.a(SourceFile:37)
 at vc.b(SourceFile:1271)
 at vc$$Lambda$2740/1247224568.run(Unknown Source)
 at afy.execute(SourceFile:77)
 at vc.b(SourceFile:1270)
 at vc$$Lambda$2739/394749531.accept(Unknown Source)
 at java.util.Optional.ifPresent(Optional.java:159)
 at vc.a(SourceFile:1270)
 at bfx.a(SourceFile:252)
 at brt.a(SourceFile:156)
 at brt.g(SourceFile:150)
 at bfx.K(SourceFile:620)
 at vc.a(SourceFile:400)
 at net.minecraft.server.MinecraftServer.b(SourceFile:816)
 at net.minecraft.server.MinecraftServer.a(SourceFile:755)
 at dwb.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 thread
Stacktrace:
 at apa.a(SourceFile:72)
 at aoy.a(SourceFile:37)
 at vc.b(SourceFile:1271)
 at vc$$Lambda$2740/1247224568.run(Unknown Source)
 at afy.execute(SourceFile:77)
 at vc.b(SourceFile:1270)
 at vc$$Lambda$2739/394749531.accept(Unknown Source)
 at java.util.Optional.ifPresent(Optional.java:159)
 at vc.a(SourceFile:1270)
 at bfx.a(SourceFile:252)
 at brt.a(SourceFile:156)
 at brt.g(SourceFile:150)

-- Block entity being ticked --
Details:
 Name: minecraft:barrel // brt
 Block: Block\{minecraft:barrel}[facing=north,open=false]
 Block location: World: (187,73,41), Chunk: (at 11,4,9 in 11,2; contains blocks 176,0,32 to 191,255,47), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
 Block: Block\{minecraft:barrel}[facing=north,open=false]
 Block location: World: (187,73,41), Chunk: (at 11,4,9 in 11,2; contains blocks 176,0,32 to 191,255,47), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Stacktrace:
 at bfx.K(SourceFile:620)
 at vc.a(SourceFile:400)

-- Affected level --
Details:
 Level name: 190201 Taking Off
 All players: 0 total; []
 Chunk stats: ServerChunkCache: 2025
 Level seed: -6855833333329500165
 Level generator: ID 00 - default, ver 1. Features enabled: true
 Level generator options: {}
 Level spawn location: World: (200,63,100), Chunk: (at 8,3,4 in 12,6; contains blocks 192,0,96 to 207,255,111), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
 Level time: 4611389 game time, 7105 day time
 Level dimension: 0
 Level storage version: 0x04ABD - Anvil
 Level weather: Rain time: 10443 (now: true), thunder time: 1989 (now: true)
 Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: true
Stacktrace:
 at net.minecraft.server.MinecraftServer.b(SourceFile:816)
 at net.minecraft.server.MinecraftServer.a(SourceFile:755)
 at dwb.a(SourceFile:128)
 at net.minecraft.server.MinecraftServer.run(SourceFile:630)
 at java.lang.Thread.run(Thread.java:745)

-- System Details --
Details:
 Minecraft Version: 19w11b
 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: 1257940472 bytes (1199 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.

I have this error frequently rendering the game unplayable. The error first occurred primarily with barrels, particularly those already in the world, now the game crashes at random points, usually relating to the use of a UI. This is in snapshot 19w11a and b - the issue began with the 'a' snapshot.

I have now noticed this with smokers and composters placed before 19w11a as well. I'm thinking it might be an issue where these are now villager work sites, but weren't when they were placed, and the world update isn't getting their data right?

I've also had this happen with blast furnaces, smokers, and brewing stands placed before updating to 19w11a (and 11b), but not normal furnaces or chests, so it definitely seems to be related to them now being villager work sites.

Exists in 12a

19w12a the ticking entity has moved from the barrels to conduits.

The issue persists also in 19w14a: 

Does this issue happen in a freshly generated world or in a world upgraded from 1.13.2 (or earlier versions)? If it happens under those scenarios please provide detailed reproduction steps. If possible, please also attach a world where it happens.

I did have this issue as of last snapshot, but due to it preventing quite a few players from joining i reset there specific regions. My map was generated using the 1st 1.14 Snapshot

Thanks for your message Adrian!

The world was generated in a 1.14 snapshot, version 19w09a if I am not mistaken. The chest or barrel in question seems to be right in the chunk where my player is located. Whenever loading up the world in either of the snapshots version 19w09a or later, the game crashes before any chunks are actually visible. See the crash report attached earlier for reference. The world first crashed while the container was open. Maybe that caused its contents to corrupt? 

Please find the world file here: 

Also, I am playing on MacOS High Sierra, Version 10.13.2. 

Best, Phime

EDIT: I could not upload the file (74,8 MB) as it exceeds the size limit set by the administrator (10MB). I would be willing to submit it another way if possible.  

Hi @unknown! If you could upload your world to Dropbox or Google Drive (or something similar) and provide us with a link to it, that would be fantastic. Thanks.

Hi Adrian, Thanks for the tip. I uploaded it to Google Drive here: https://drive.google.com/open?id=1_0R6sYEe_i_OwQpjgZdMJ1FB3s-rrqFk 

Confirmed with given world. Thanks!