mojira.dev
BDS-10231

Server crashes after connect

This happens when starting the server and connecting

 

[INFO] Server started.
[INFO] Player connected: XXXXXXXXXXX, xuid: XXXXXXXXXXXXX
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.101.1
OS: Linux
Server start: 2020-11-29 16:42:15 CET
Dmp timestamp: 2020-11-29 16:42:46 CET
Upload Date: 2020-11-29 16:42:46 CET
Session ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Commit hash:
Build id: development
CrashReporter Key: 6428d53a-f3c1-3066-b082-c1e61f315eb1

Crash
[INFO]  at std::vector<ItemStack, std::allocator<ItemStack> >::size[] const (UnknownFile:?)
       at FillingContainer::serverInitItemStackIds[int, int, std::function<void [int, ItemStack const&]>] (UnknownFile:?)
       at ChestBlockActor::serverInitItemStackIds[int, int, std::function<void [int, ItemStack const&]>] (UnknownFile:?)
       at ContainerModel::serverInitItemStackIds[] (UnknownFile:?)
       at ContainerManagerModel::_serverInitItemStackIds[ContainerModel*] (UnknownFile:?)
       at ContainerManagerModel::serverInitItemStackIds[] (UnknownFile:?)
       at InventoryContentPacket::fromPlayerInventoryId[ContainerID, Player&] (UnknownFile:?)
       at VanillaServerGameplayEventListener::onPlayerOpenContainer[Player&, ContainerType, BlockPos const&, ActorUniqueID] (UnknownFile:?)
       at std::function<EventResult [gsl::not_null<PlayerEventListener*>]>::operator[][gsl::not_null<PlayerEventListener*>] const (UnknownFile:?)
       at EventCoordinator<PlayerEventListener>::processEvent[std::function<EventResult [gsl::not_null<PlayerEventListener*>]>] (UnknownFile:?)
       at PlayerEventCoordinator::sendPlayerOpenContainer[Player&, ContainerType, BlockPos const&, ActorUniqueID] (UnknownFile:?)
       at ChestBlockActor::openBy[Player&] (UnknownFile:?)
       at ChestBlock::use[Player&, BlockPos const&, unsigned char] const (UnknownFile:?)
       at Block::use[Player&, BlockPos const&, unsigned char] const (UnknownFile:?)
       at GameMode::useItemOn[ItemStack&, BlockPos const&, unsigned char, Vec3 const&, Block const*] (UnknownFile:?)
       at SurvivalMode::useItemOn[ItemStack&, BlockPos const&, unsigned char, Vec3 const&, Block const*] (UnknownFile:?)
       at std::function<void []>::operator[][] const (UnknownFile:?)
       at Container::createTransactionContext[std::function<void [Container&, int, ItemStack const&, ItemStack const&]>, std::function<void []>] (UnknownFile:?)
       at PlayerInventory::createTransactionContext[std::function<void [Container&, int, ItemStack const&, ItemStack const&]>, std::function<void []>] (UnknownFile:?)
       at ItemUseInventoryTransaction::handle[Player&, bool] const (UnknownFile:?)
       at ServerNetworkHandler::handle[NetworkIdentifier const&, InventoryTransactionPacket const&] (UnknownFile:?)
       at PacketHandlerDispatcherInstance<InventoryTransactionPacket, false>::handle[NetworkIdentifier const&, NetEventCallback&, std::shared_ptr<Packet>&] const (UnknownFile:?)
       at Packet::handle[NetworkIdentifier const&, NetEventCallback&, std::shared_ptr<Packet>&] (UnknownFile:?)
       at NetworkHandler::_sortAndPacketizeEvents[NetworkHandler::Connection&, std::chrono::time_point<std::chrono::_V2::system_clock, std::chrono::duration<long, std::ratio<1l, 1000000000l> > >] (UnknownFile:?)
       at NetworkHandler::runEvents[bool] (UnknownFile:?)
       at Minecraft::update[] (UnknownFile:?)
       at ServerInstance::_update[] (UnknownFile:?)
       at clone (UnknownFile:?)

 

 

 

 

Replacing the world with an old Version fixes the issue.

 

 

Attachments

Comments 9

It appears that there is an issue with a chest entity.

Had this happen on our server also.  Identified the chest in-game (see screenshot).

Opening the chest causes a crash,  Breaking the chest with an axe seems to be sufficient to repair the damaged data.

It appears that there is an issue with a chest entity.

Had this happen on our server also.  Identified the chest in-game (see screenshot).

Opening the chest causes a crash,  Breaking the chest with an axe seems to be sufficient to repair the damaged data.

Further Information:

This appears to only happen to Double Chests, and only when the two component parts of the chest are in different chunks. 

Possibly caused by the updating of the chunks into 1.16.100

Further Information:

This appears to only happen to Double Chests, and only when the two component parts of the chest are in different chunks. 

Possibly caused by the updating of the chunks into 1.16.100

Have you got a copy of the world file from when the corrupted chest was still there?

I can often forward crash reports that have a reproducible world attached but if the world is no longer available we usually leave it to the automatic crash logging Mojang receives when BDS crashes.

Have you got a copy of the world file from when the corrupted chest was still there?

I can often forward crash reports that have a reproducible world attached but if the world is no longer available we usually leave it to the automatic crash logging Mojang receives when BDS crashes.

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Flo

(Unassigned)

Unconfirmed

awaiting-response

Retrieved