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

Start by reviewing the attached coredumpctl.txt, dmesg.txt, and stdio.txt logs, then reproduce the destruction event with a remote client over a high-latency connection in Basic Battle or Beacon of Light. Done means the Linux client or server no longer segfaults when the destroyed-ship static is displayed in either connection configuration.