Linux crash Issue

ID:117060
 
Aug 11 2011, 10:22 am
BYOND Version:489
Operating System:CentOS
Web Browser:Chrome 13.0.782.112
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.
Crashes everytime.
BUG: Crashing due to an illegal operation!
proc name: human hud (/obj/hud/proc/human_hud)
  usr:  (/mob/living/carbon/human)
  src: the hud (/obj/hud)
  call stack:
the hud (/obj/hud): human hud()
the hud (/obj/hud): instantiate()
the hud (/obj/hud): New( (/mob/living/carbon/human))
 (/mob/living/carbon/human): Login()
 (/mob/living/carbon/human): Login()
/datum/mind (/datum/mind): transfer to( (/mob/living/carbon/human))
Spaceman96 (/mob/new_player): create character()
/datum/controller/gameticker (/datum/controller/gameticker): create characters()
/datum/controller/gameticker (/datum/controller/gameticker): setup()
/datum/controller/gameticker (/datum/controller/gameticker): pregame()

Backtrace for BYOND 489.1099 on Linux:

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804a708]
libbyond.so 0x342ea0, 0x34379b
libc.so.6 [0xb7748000, 0x0], 0x28e90
libbyond.so 0x342ea0, 0x34379b
libbyond.so 0x334bd0, 0x334d2e
libbyond.so 0x334fa0, 0x334ff2
libbyond.so 0x29c9f0, 0x29cadd
libbyond.so 0x2090d0, 0x2092a2
libbyond.so 0x210200, 0x2104ab
libbyond.so [0xb7bb7000, 0x0], 0x21ef96
libbyond.so 0x21fa00, 0x21fae4
libbyond.so [0xb7bb7000, 0x0], 0x24c97b
libbyond.so [0xb7bb7000, 0x0], 0x24ce77
libbyond.so 0x255150, 0x25522a
libbyond.so [0xb7bb7000, 0x0], 0x275236
libbyond.so [0xb7bb7000, 0x0], 0x267376
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed
libbyond.so [0xb7bb7000, 0x0], 0x27477d
libbyond.so [0xb7bb7000, 0x0], 0x261c41
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed
libbyond.so [0xb7bb7000, 0x0], 0x27477d
libbyond.so [0xb7bb7000, 0x0], 0x25ce41
libbyond.so 0x2730e0, 0x2731f0
libbyond.so [0xb7bb7000, 0x0], 0x27c081
libbyond.so [0xb7bb7000, 0x0], 0x2646cb
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed
libbyond.so 0x275460, 0x275518
libbyond.so 0x214bf0, 0x215049
libbyond.so 0x2156c0, 0x2156e5
libbyond.so [0xb7bb7000, 0x0], 0x2538cb
libbyond.so 0x255150, 0x2552c3
libbyond.so [0xb7bb7000, 0x0], 0x275236
libbyond.so [0xb7bb7000, 0x0], 0x267376
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed
libbyond.so [0xb7bb7000, 0x0], 0x27477d
libbyond.so [0xb7bb7000, 0x0], 0x261c41
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed
libbyond.so [0xb7bb7000, 0x0], 0x27477d
libbyond.so [0xb7bb7000, 0x0], 0x261c41
libbyond.so 0x2730e0, 0x2731f0
libbyond.so 0x273240, 0x2732ed



Expected Results:
Running fine.
Actual Results:
Crashes
Does the problem occur:
Every time as soon as someone joins.

When does the problem NOT occur?
Never
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? 488

Workarounds:
Downgrading to 488 works.
Aug 12 2011, 7:29 am
This crash is occurring in a routine to read a .dmi file. Based on what I'm seeing it looks like it happened under memory stress and an allocation failed. 488 probably wouldn't make much or any difference here; it seems more likely that something was happening on your system at the time that caused it to eat up too much memory.

It would probably help to see a copy of the icon in question to see if there's anything in it that might confuse the load routine, but I think that's a long shot. As it stands right now this doesn't look like anything we can reproduce.