This bug is completely random but it has been happening a lot more recently. Shell Server keeps going down but the games it hosts remain live. The problem is that people can't manage their games if they don't have the verbs in their games to manage them now.
BUG: Crashing due to an illegal operation!
Backtrace for BYOND 509.1318 on Linux:
Generated at Mon May 23 14:31:52 2016
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb24]
libbyond.so [0xb7280000, 0x0], 0x320ba9
[0xb77ca000, 0xb77ca600], [0xb77ca000, 0xb77ca600]
libbyond.so [0xb7280000, 0x0], 0x320ba9
libbyond.so [0xb7280000, 0x0], 0x3211fe
libbyond.so [0xb7280000, 0x0], 0x2e8b37
libbyond.so [0xb7280000, 0x0], 0x2db339
libbyond.so [0xb7280000, 0x0], 0x2dcd8c
libbyond.so [0xb7280000, 0x0], 0x2dca86
libbyond.so [0xb7280000, 0x0], 0x2de378
libbyond.so [0xb7280000, 0x0], 0x2de845
libbyond.so 0x2e0970, 0x2e10ed
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ae34]
libc.so.6 0x16d60, 0x16e46 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a731]
Recent proc calls:
/proc/StatLoop
/proc/StatLoop
/mob/Logout
/mob/Stat
/mob/proc/isTyping
/mob/proc/isTyping
/mob/proc/labelSet
/mob/Stat
/mob/Stat
/proc/timestamp
/proc/StatLoop
/proc/StatLoop
/mob/Stat
/mob/proc/isTyping
/mob/proc/isTyping
/mob/proc/labelSet
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
Numbered Steps to Reproduce Problem:
I have absolutely no clue. But, I'm starting to question the people who are reporting the server manager being down to see if there's any correlation with what they were doing last on the server manager.
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.) It has honestly always occurred and I've done other bug reports on this.
This report isn't really helpful but it's better than making no report at all. Hopefully I get some valuable information that I can post here and this issue gets resolved.
If you need any code snippets for the recent procedures, let me know. I'm open to posting them.
I would however recommend switching to 510, as it's far enough along that there's a chance whatever caused this was already fixed.