My friend and I were using a bedrock server first to play together but BDS-11039 / BDS-10666 kicked in. Hoping realms will not have the same issue I've uploaded our world and started playing. I believe the very same issue haunts us on realm as well, after logging in (being in the middle of a village) the realm crashes and rolls back.
I've downloaded the world, and will try the workaround (which made bedrock server stable again) on realm too: removing all beds in the village(s) we're in currently. Locally the world doesn't make the app crash, so it is possible to do it. Once it's done and I've uploaded the world again, I'll let you know the results. If it will not disconnect us any more (as it does now always) then it must be the same bug as BDS-11039 / BDS-10666 tracks. Will see (tomorrow).
I have Ubuntu 18.04.5 LTS and libc 2.27 (Ubuntu GLIBC 2.27-3ubuntu1.4), and the crash is still happening for me, right after join, within a min. Consistently.
I upgraded libc:
linux-libc-dev:amd64 (4.15.0-124.127, 4.15.0-128.131)
And then it all happened with that 1.16.200.02 version of bedrock server. Now an updated bedrock server came out (assuming was compiled with later libc) and now it seems to be fine again.
Could u guys try to upgrade libc and bedrock server?
It's happening on 1.16.200.02 too. I'm putting the stacktrace here, but assuming it's the same.
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.200.2
OS: Linux
Server start: 2020-12-14 14:14:23 CET
Dmp timestamp: 2020-12-14 14:15:24 CET
Upload Date: 2020-12-14 14:15:24 CET
Session ID: 077045b1-a757-4b31-98ec-fe3d6a527c8f
Commit hash:
Build id: development
CrashReporter Key: d210ab83-12c9-38ec-8491-ad409c7bd8ab
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:?)
NO LOG FILE! - Failed to up file descriptor limit Operation not permitted
NO LOG FILE! - setting up server logging...
[2020-12-14 14:15:24 INFO] Starting Server
[2020-12-14 14:15:24 INFO] Version 1.16.200.2
[2020-12-14 14:15:24 INFO] Session ID 019d5b15-c916-4dae-afa5-d5cf7eeb681f
[2020-12-14 14:15:24 INFO] Level Name: iceworld
[2020-12-14 14:15:24 INFO] Game mode: 0 Survival
[2020-12-14 14:15:24 INFO] Difficulty: 1 EASY
[INFO] opening worlds/iceworld/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] IPv4 supported, port: 51442
[INFO] IPv6 supported, port: 47872
[INFO] Server started.
I just need to log into server, and wait a minute and it crashes. (My character is in a village ofc)
Let me know if u need the world to reproduce.
Thanks
I removed all beds around us locally, and then uploaded the world to realm. I was there for two mc days without disconnects. I'd say this is the workaround, but will play on realm more to be sure.
So it seems it's the same bug what I mentioned here: https://bugs.mojang.com/browse/REALMS-6812?focusedCommentId=899573&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-899573