BDS-3092Using Stop command on Ubuntu 18.04 causes crash
Reproducing on 1.14.21 - Issue has existed for several revisions.
When using the Stop command from the Console, no players are connected, the server crashes on exit.
stop
terminate called after throwing an instance of 'std::bad_variant_access'
what(): Unexpected index
[2020-02-05 22:24:30 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.14.21.0
OS: Linux
Server start: 2020-02-05 22:07:54 PST
Dmp timestamp: 2020-02-05 22:24:30 PST
Upload Date: 2020-02-05 22:24:30 PST
Session ID: c130956d-a20d-45aa-b59a-230c2d912134
Commit hash:
Build id: development
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Environment
Distributor ID: Ubuntu
Description: Ubuntu 18.04.3 LTS
Release: 18.04
Samsung 500g SSD
Quad Processor - Xeon #7-4850 @ 2.0 GHZ
Attachments4
Comments9
History8
Added affects versions: 1.14.30
Added labels: awaiting-response
Added Confirmation Status: Unconfirmed
Removed labels: awaiting-response
Resolution: Unresolved → Invalid
Does this happen consistently for you? Even with a new world?
I run 3 BDS servers on Windows and don't get the same error, just trying to help narrow down if its specific to the OS or the world files.
Confirmed that if I make a new server on the Ubuntu that it is not having the problems. However when I transferred the world files from the other existing world to windows, it had no problems as well.
So it seems to only happen with the world while being run on Ubuntu.
Is there some sort of repair I can do on the environment?
1.14.30.2 — Still experiencing the issues. If no users connect to the server, it does not crash on shutdown.
If a user connects and disconnects, if the server is topped, it will crash.
Hi Ben,
A new update came out a couple of days ago that includes a bunch of crash fixes for BDS, are you able to give this another test on that?
Ionic
I can reproduce on Ubuntu. I have also since experienced it on Windows.
but it is less common. Crash_REport_Windows_Stop_1_14_32_1.txt
I have noticed if I start up the server and just stop it it rarely happens.
It is 100% if a user is connected which is expected.
I thought it might have something to do with ticking areas being enabled as turning that off helped reduce it but not 100%.
I
I'm seeing the same behavior which occurs after a user tries to log onto the server but gets an erroneous "the account is already logged on from a different device" message. I'm not sure if they're related but I see this error everything that occurs and I need to stop and restart the server.
I experience the same problem as Ben described. Output looks very similar. Server crashed after stop command was given. Server had been running for two weeks. Last user logged off 15 minutes before the stop command was given.
Ubuntu linux, latest version BDS.
I've not been able to reliably reproduce this issue (but I agree that sporadically I've also had it happen).
We only track specific crashes that can be reliably reproduced here on the bug tracker. Trying to track when a random crash is fixed isn't feasible for us and in this case I've noted that the error is not always the same, indicating different causes.
Crashes like this that are more random are tracked and handled internally by the development team.
If you need help or have a suggestion you might like to follow a link below. Alternatively, if you have reproduction steps for the issue that work on a brand new vanilla world feel free to raise a new report.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs