Me and Oof laddie have been crashing Bridgewater-Brunel a lot lately, and the only explanation we can come up with for it is us chatting at the same time. Here's a link to a save I made after the latest crash. (https://files.huitsi.net/tmp/justcrashed.sve) In case it matters, I'm using the Linux client.
No texting and driving - trains or busses or planes! :)
Quote from: Huitsi on July 03, 2025, 12:05:55 PMMe and Oof laddie have been crashing Bridgewater-Brunel a lot lately, and the only explanation we can come up with for it is us chatting at the same time. Here's a link to a save I made after the latest crash. (https://files.huitsi.net/tmp/justcrashed.sve) In case it matters, I'm using the Linux client.
Thank you for the report.
Can you confirm whether the game reboots immediately after the crash or whether you have to wait until the next day?
Also, does it *always* crash when more than one person sends a chat message within a particular period of time? If not, there is a very high chance that the chatting is not the cause of this and a lot, lot more work will be needed to find the cause.
(The general principle is that, to be confident of finding the cause, we need not only evidence that is consistent with it being the cause, but evidence that is inconsistent with anything else being the cause).
The server does not reboot immediately after the crash.
Whether the crash always happens when multiple people chat within a period of time or what said period of time might be is unfortunately a lot trickier to say. With the server not rebooting quickly (and my failure run a connectable-to server), we couldn't really test this to the degree necessary to determine that.
I, too, thought it unlikely at first, but after many crashes – and discussions on what we were doing at the time – it is difficult to come up with any other explanation. Of course, we can't be 100% sure since each crash has happened while playing the game rather than intentionally trying to crash the server.
The crashes where you have to wait until the next day to reboot are typically thread deadlocks. We have never been able to get a reliable reproduction case for this type of problem.
Without a reliable reproduction case, the prospect of fixing this is very slim indeed.
I may have just caused this just by trying to say "hi" to Oof, presumably without them chatting at the same time...