We were playing, as usual, then someone got killed by a Zombie. And everyone got disconnected cause the server crashed.
Here is the log output:
[2020-08-02 18:13:12 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.1.2
OS: Linux
Server start: 2020-08-01 06:40:50 CST
Dmp timestamp: 2020-08-02 18:13:12 CST
Upload Date: 2020-08-02 18:13:12 CST
Session ID: 68e31b34-e03c-491c-ae89-ebf200554dca
Commit hash:
Build id: development
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[2020-08-02 18:13:12 INFO] at Scoreboard::shouldClearScoresOnDeath[Actor const&] (UnknownFile:?)
at Level::removeEntityReferences[Actor&, bool] (UnknownFile:?)
at Level::forceRemoveEntity[Actor&] (UnknownFile:?)
at Dimension::removeActorByID[ActorUniqueID const&] (UnknownFile:?)
at Level::addEntity[BlockSource&, std::unique_ptr<Actor, std::default_delete<Actor> >] (UnknownFile:?)
at LevelChunk::_deserializeEntity[BlockSource&, IDataInput&, std::vector<ActorLink, std::allocator<ActorLink> >&] (UnknownFile:?)
at LevelChunk::tick[BlockSource&, Tick const&] (UnknownFile:?)
at Player::tickWorld[Tick const&] (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:?)
9eb4921e-5359-403e-a6d7-ca37a87c7c33Comments 4
Just a couple of things on this one.
Just as an FYI, Java is not needed for BDS. I noticed you included your Java version in the report and just wanted to make sure you weren't expecting it to be used for your BDS instance.
The error seems to be something to do with a custom scoreboard. If you're using a custom behaviour pack or scoreboard related command block addon (likely related to deaths) you may find disabling it prevents the crash from happening (as a workaround).
As for the crash itself. Crashes are automatically logged to Mojang along with a bunch of supporting data to help them resolve it. Because of the random nature of crashes we don't track them here as it would be impossible to know when one was fixed.
They are however tracked and resolved internally by Mojang.
Thank you for your report!
Crashes such as these are now logged automatically, this will therefore be investigated further by the development team internally.
If you need help or have a suggestion you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
Thank you for your report!
Crashes such as these are now logged automatically, this will therefore be investigated further by the development team internally.
If you need help or have a suggestion you might like to follow a link below.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
Just a couple of things on this one.
Just as an FYI, Java is not needed for BDS. I noticed you included your Java version in the report and just wanted to make sure you weren't expecting it to be used for your BDS instance.
The error seems to be something to do with a custom scoreboard. If you're using a custom behaviour pack or scoreboard related command block addon (likely related to deaths) you may find disabling it prevents the crash from happening (as a workaround).
As for the crash itself. Crashes are automatically logged to Mojang along with a bunch of supporting data to help them resolve it. Because of the random nature of crashes we don't track them here as it would be impossible to know when one was fixed.
They are however tracked and resolved internally by Mojang.