Unknown Crash?

ID:1386552
 
Sep 27 2013, 8:34 am
BYOND Version:500.1210
Operating System:Linux
Web Browser:Chrome 28.0.1500.71
Applies to:Dream Daemon
Status: Unverified
Thus far we've been unable to verify or reproduce this bug. Or, it has been observed but it cannot be triggered with a reliable test case. You can help us out by editing your report or adding a comment with more information.
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 500.1210 on Linux:
Generated at Fri Sep 27 12:00:57 2013

6000 [0x8048000, 0x0], [0x8048000, 0x804ab18]
libbyond.so 0x348220, 0x34823f
 [0xf77bd000, 0xf77bd410], [0xf77bd000, 0xf77bd410]
libbyond.so 0x348220, 0x34823f
libbyond.so [0xf727c000, 0x0], 0x2b2292
libbyond.so 0x349a00, 0x349c13
libbyond.so 0x318720, 0x318929
6000 [0x8048000, 0x0], [0x8048000, 0x804a5ac]
libc.so.6 0x19840, 0x19935 (__libc_start_main)
6000 [0x8048000, 0x0], [0x8048000, 0x8049ff1]

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 honestly don't know what caused it. Nobody was doing anything. My best guess is that it's something to do with Login() and Logout() procedures.
Sep 27 2013, 11:26 am
This is very strange. I looked at your trace, and it says this happened when a timer for handling background procs was removed. The timer was apparently corrupt.

Unfortunately, I don't have any further info on the nature of the corruption, though if you have a core dump that might be something I can work with; there's a chance it might be able to tell me something useful. I have a feeling this was a one-off event or was caused by some other bug, but who knows. If you see this thing happen again please post followups.
Sep 27 2013, 1:07 pm
Mind naming all the -options you would like me to run with DreamDaemon?

-core being one.
Sep 28 2013, 12:55 pm
 
BUG: Crashing due to an illegal operation!

Backtrace for BYOND 500.1210 on Linux:
Generated at Sat Sep 28 18:54:15 2013

6000 [0x8048000, 0x0], [0x8048000, 0x804ab18]
libbyond.so 0x348220, 0x34823f
 [0xf77d9000, 0xf77d9410], [0xf77d9000, 0xf77d9410]
libbyond.so 0x348220, 0x34823f
libbyond.so [0xf727d000, 0x0], 0x2b2292
libbyond.so 0x349a00, 0x349c13
libbyond.so 0x318720, 0x318929
6000 [0x8048000, 0x0], [0x8048000, 0x804a5ac]
libc.so.6 0x19840, 0x19935 (__libc_start_main)
6000 [0x8048000, 0x0], [0x8048000, 0x8049ff1]

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/


I paged you a link to the core file as well. I didn't know whether or not it was safe to publicly display the core file.
Sep 30 2013, 11:14 am
Darnit, either I'm doing something wrong or the core file dumped at a spot I can't get at. The former is more likely. I'm not getting any useful info out of this core.
Sep 30 2013, 11:29 am
Bagh. I hope it works eventually. It'd suck if all that occurred with no results.
Sep 30 2013, 11:53 am
Well at the very least we've established it isn't a one-off. Though you've had enough other issues that I wonder if there's more going on here related to your OS.
May 14 2014, 11:24 pm
Hello Xirre. Any repeats of this issue? We've obviously moved on a bit version-wise, so I'm keen to get up to date crash reports, or just close the bug report down.
May 15 2014, 9:45 pm
They come and go. It's very rare. I don't even run my server with -core on anymore. When core dump is enabled it appears that child DreamDaemon's also, by default, get their core dumps enabled. As such, poorly programmed games start getting core dumps that are 150MB large. I don't have the disk space for such a thing. Would that also be a bug? If so, I can make a report on it.
May 15 2014, 11:10 pm
I dunno, as it's a child process, I expect it to inherit all of it's parents process attributes, so I don't think that's a bug.
May 15 2014, 11:10 pm
Stephen001 changed status to 'Unverified'