EmptyEpsilon
EmptyEpsilon copied to clipboard
segfault when ship is destroyed on Ubuntu 20.04/Linux Mint 20)
Version: EE-2022.03.16, deb package
Segfault happens on Ubuntu 20.04 and Linux Mint 20 (itself a derivative of Ubuntu 20.04) when the ship is destroyed (when the static should be displayed). Logs are attached from Mint box.
The game needs at least 1 remote client connected with relatively high latency (several hops, one of them through SSH tunnel). I didn't reproduce this on LAN, but with remote connection it reproduced reliably. One of the machines was Windows. Segfault on Linux happens in both configurations: when Linux is a server and Windows is a client and also vice versa. Two scenarios were tried, Basic Battle and Beacon of Light.
coredumpctl.txt dmesg.txt stdio.txt
(Sorry for the redactions, and I'm not comfortable posting raw cores; I still have them though and I can post additional info if you need).
This is probably not a duplicate #1741, I think I've reproduced the other one (with 2022.03.16 on Mint) and bt differs.
cc @greenhammock @bfugas
I know currently operations crashes when a ship is destroyed in that version (it's fixed in master), which I think is what the dump is also pointing at (don't need raw core dumps, this stacktrace is already great)
But it could be that a different station has the same bug?
But it could be that a different station has the same bug?
I don't understand the question. Which "different station" do you mean?
like, what was the person viewing when the game crashed? The 3/4 player "operations" view crashes in the current release when your ship is destroyed, but I didn't check all other possible views.
Ah, sorry. I was thinking about space stations. I'll check in the evening.
yeah, I should avoid using the word "Station" it means 3 different things in the EmptyEpsilon context :D
Didn't spot any other station (like, crew station) crashing, and I think I've died at most of them. Didn't test Tactical.