It's a simple summary. I am hosting a SS13 (space station 13) server externally on a linux-based host - and we keep getting crashes. each time, it redirects me here with the following message(see below)
Numbered Steps to Reproduce Problem:
Code Snippet (if applicable) to Reproduce Problem:
Expected Results:
Actual Results:I cannot recreate it, because I don't know what is causing it...
Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?
When does the problem NOT occur?
It didn't occur for a week, then it started randomly and hasn't stopped happening. That is all I know.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Workarounds:
The error code:
Backtrace for BYOND 499.1197 on Linux:
Generated at Sun Oct 20 15:21:17 2013
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a8ce]
libbyond.so 0x3a3b70, 0x3a47be
[0xb7861000, 0xb786140c], [0xb7861000, 0xb786140c]
libbyond.so 0x3a3b70, 0x3a47be
libbyond.so 0x396830, 0x39699e
libbyond.so 0x396a50, 0x396a91
libbyond.so 0x2ef690, 0x2ef7aa
libbyond.so 0x2f2820, 0x2f3585
libbyond.so 0x2f4060, 0x2f40e1
libbyond.so 0x2f4a60, 0x2f4b6c
libbyond.so 0x2ef690, 0x2ef6dc
libbyond.so 0x2f2820, 0x2f3585
libbyond.so 0x2f4060, 0x2f40e1
libbyond.so 0x2f9680, 0x2f99f3
libbyond.so 0x2fa530, 0x2fa5c1
libbyond.so [0xb72f3000, 0x0], 0x2b0483
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so [0xb72f3000, 0x0], 0x2c6a52
libbyond.so [0xb72f3000, 0x0], 0x2b122c
libbyond.so 0x2c5360, 0x2c546b
libbyond.so [0xb72f3000, 0x0], 0x2b8657
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so [0xb72f3000, 0x0], 0x2c68ec
libbyond.so [0xb72f3000, 0x0], 0x2a95b9
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so [0xb72f3000, 0x0], 0x2c6a52
libbyond.so [0xb72f3000, 0x0], 0x2b122c
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so [0xb72f3000, 0x0], 0x2c68ec
libbyond.so [0xb72f3000, 0x0], 0x2b122c
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so [0xb72f3000, 0x0], 0x2c68ec
libbyond.so [0xb72f3000, 0x0], 0x2b122c
libbyond.so 0x2c5360, 0x2c546b
libbyond.so 0x2c54e0, 0x2c5593
libbyond.so 0x2c7730, 0x2c77fc
libbyond.so [0xb72f3000, 0x0], 0x2c90e9
libbyond.so 0x2c54e0, 0x2c568d
libbyond.so 0x2c7730, 0x2c77fc
libbyond.so 0x273b60, 0x273c73
libbyond.so [0xb72f3000, 0x0], 0x2751da
libbyond.so [0xb72f3000, 0x0], 0x2883ca
libbyond.so 0x289450, 0x2894cf
libbyond.so 0x2d5e60, 0x2d5ef9
libbyond.so 0x328f30, 0x329206
To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1
DreamDaemon will now produce a file called 'core' that you can send to the
BYOND developers for more analysis. For instructions, please contact us at
http://www.byond.com/support/
http://www.byond.com/download/build/499/
Tom mentioned in his post that that version fixes a heap corruption issue for Linux users, which may be what you're seeing. I can't find any mention of which program the fix was for, but it's worth a try.