BYOND core segfault crashes from time to time in hosting server.
Numbered Steps to Reproduce Problem:
Don't know the cause exactly, but throughout hosting it will crash from time to time, mostly when a new round starts/ends, but not always.
Code Snippet (if applicable) to Reproduce Problem:
Application: dreamdaemon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6D3F9675
Stack:
Faulting application name: dreamdaemon.exe, version: 5.0.512.1488, time stamp: 0x5d94fd60
Faulting module name: byondcore.dll, version: 5.0.512.1488, time stamp: 0x5d94fce6
Exception code: 0xc0000005
Fault offset: 0x00129675
Faulting process id: 0x47c
Faulting application start time: 0x01d5afcc913aff15
Faulting application path: C:\TGS\TGMC\BYOND\bin\dreamdaemon.exe
Faulting module path: C:\TGS\TGMC\BYOND\bin\byondcore.dll
Report Id: 16c92235-1bc5-11ea-80eb-00155d081311
Faulting package full name:
Faulting package-relative application ID:
I have several crash dumps that can annex, each with around 13MB.
Last one, related to this event: (EDIT: old link)
I would recommend trying to switch to 513, because it's possible that some of the fixes made since 512.1488 have rendered this issue moot.
It's also possible that your server was out of memory, which can cause all sorts of weird issues as things fail to allocate and not everything is sanity-checked. If that's the case, 513 is unlikely to help but you can look for ways to decrease the server's memory footprint. The big question is whether this is possibly the case; it would help to know what typical memory usage looks like for your server. If you have other crash reports that show a different offset for the crash, then I think memory exhaustion is a very strong candidate.