ID:1905339
 
BYOND Version:508
Operating System:Linux
Web Browser:Firefox 39.0 (Doesn't matter)
Applies to:Dream Daemon
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:

Numbered Steps to Reproduce Problem:

Expected Results: Normal working

Actual Results: Server crashing


Does the problem occur:
Every time? Or how often? Not tested
In other games? Only SS13
In other user accounts? It's a server
On other computers? It's a server

When does the problem NOT occur? I don't 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.)
I don't know

Logs:
Backtrace for BYOND 508.1293 on Linux:
Generated at Mon Jul 27 17:07:45 2015

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bb24]
libc.so.6 0x69cf0, 0x69d21 (fseek)
[0xf774a000, 0xf774a410], [0xf774a000, 0xf774a410]
libc.so.6 0x69cf0, 0x69d21 (fseek)
libbyond.so [0xf7216000, 0x0], 0x2d9134
libbyond.so [0xf7216000, 0x0], 0x2da6cc
libbyond.so [0xf7216000, 0x0], 0x254a84
libbyond.so [0xf7216000, 0x0], 0x2dae78
libbyond.so [0xf7216000, 0x0], 0x2dba55
libbyond.so 0x2dd430, 0x2dd7bb
libbyond.so 0x2dd8f0, 0x2ddafd
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ae34]
libc.so.6 0x19840, 0x19935 (__libc_start_main)
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a731]

Recent proc calls:
/proc/list2text
/proc/station_name
/world/proc/update_status
/proc/moveRange
/proc/cmp_name_asc
/proc/cmp_name_asc
/proc/cmp_name_asc
/datum/sortInstance/proc/gallopRight
/proc/moveElement
/proc/cmp_name_asc
/proc/moveElement
/proc/cmp_name_asc
/proc/moveElement
/proc/cmp_name_asc
/proc/moveElement
/proc/cmp_name_asc

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
I'm not at a good stage to check this out, but I'll look into it when I can in a week or so. In the meantime please post any new issues if they come up.
Looking through this forum's history, this crash has been reported and fixed multiple times over. Kinda weird.