We hit the issue on our Bedrock server as well, similar crash stack:
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.201.2
OS: Linux
Server start: 2021-01-27 20:45:43 PST
Dmp timestamp: 2021-01-27 20:47:53 PST
Upload Date: 2021-01-27 20:47:53 PST
Session ID: 2bf4a1fd-8a19-4d84-b30b-075036697657
Commit hash:
Build id: development
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[INFO] at std::__shared_count<[__gnu_cxx::_Lock_policy]2>::__shared_count[std::__weak_count<[__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?)
at std::__shared_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2>::__shared_ptr[std::__weak_ptr<POIInstance, [__gnu_cxx::_Lock_policy]2> const&, std::nothrow_t] (UnknownFile:?)
at std::shared_ptr<POIInstance>::shared_ptr[std::weak_ptr<POIInstance> const&, std::nothrow_t] (UnknownFile:?)
at std::weak_ptr<POIInstance>::lock[] const (UnknownFile:?)
at Village::getBedPOICount[] const (UnknownFile:?)
at Village::tick[Tick, BlockSource&] (UnknownFile:?)
at VillageManager::tickVillages[Tick const&, Vec3 const&, BlockSource&] (UnknownFile:?)
at ServerPlayer::tickWorld[Tick const&] (UnknownFile:?)
at std::function<bool [Player&]>::operator[][Player&] const (UnknownFile:?)
at Level::forEachPlayer[std::function<bool [Player&]>] (UnknownFile:?)
at Level::tick[] (UnknownFile:?)
at ServerLevel::tick[] (UnknownFile:?)
at GameSession::tick[] (UnknownFile:?)
at Minecraft::tickSimtime[int, int] (UnknownFile:?)
at Minecraft::update[] (UnknownFile:?)
at ServerInstance::_update[] (UnknownFile:?)
at clone (UnknownFile:?)
We did a bunch of testing, including killing off all villagers in the affected chunk, attempting to remove all beds - made no difference. The issue occurs in the chunk containing -1871, -2140, world files uploaded for testing purposes: https://drive.google.com/file/d/1egoKVwvqRxNqzu9LZ7j72UvQktkDHz9T/view?usp=sharing
Let me know if further testing and/or access is needed, we're not shy.
I've run 4 minecraft servers on this box for 2 years (3 release, one snapshot). It has 96GB RAM and 24 CPU threads (2x 6 cores x2 HT). I have never seen this issue before loading this snapshot, and none of the other servers are affected still - just the one server running this latest snapshot. Both times it crashed it only had 2 players on it. Do you really think the issue is environmental?
Unable to repro on 1.13-pre1. Looks like this is fixed.
Sorry, been too buried in work to play MC for a while - pretty sure it still happened in 1.12.2. We now have a snapshot server up on 18w22c, will attempt a repro tonight.
Reproed last night, even a short 10-block trip triggers this effect:
Rebooted server, logged in, tamed wolf fought as normal
Loaded wolf into boat, took short trip
Destroyed boat to release wolf, wolf would not fight
Logged out and back in, wolf would not fight
Restarted server, wolf fought as normal again
Testing here, looking good so far - chalk up one more 'seems fixed'. Thanks for addressing this! We had a rather large no-go zone in our world that we are glad to return to. 🙂