Hard crashes in 510.1341

ID:2082681
 
May 11 2016, 12:54 pm
BYOND Version:1341
Operating System:Windows server 2012 r2
Web Browser:Firefox 47.0
Applies to:Dream Daemon
Status: Open
Issue hasn't been assigned a status value.
Dunno if you can glean anything from the event log
Faulting application name: dreamdaemon.exe, version: 5.0.510.1341, time stamp: 0x57291d76
Faulting module name: byondcore.dll, version: 5.0.510.1341, time stamp: 0x57291c69
Exception code: 0xc00000fd
Fault offset: 0x000c6756
Faulting process id: 0x1504
Faulting application start time: 0x01d1ab2ab92cd15d
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 611cf968-1786-11e6-80ba-0cc47ab3459f
Faulting package full name: 
Faulting package-relative application ID:
May 11 2016, 1:51 pm
That's a stack overflow. It's not good that that's not being caught properly, but that's what it is. The failure is happening within DoProc() while pushing a value to the stack.

I think to make any headway on this I'd need a full stack trace, like from WinDbg. The Linux build would have told you the last few procs called which are probably a vital clue, although the Windows build doesn't have a way to get you that info.
May 11 2016, 2:24 pm
alright i'll see what I can do
May 11 2016, 2:39 pm
Of course the most likely outcome of a stack trace will be to say that it's calling DoProc() repeatedly, so I don't know if that will help all that much, since it won't say which proc is doing all that recursion.
May 12 2016, 11:35 pm
Unsure if this is related but apparently changing an atom's icon from a DMI to a gif at runtime is causing crashes.
May 12 2016, 11:43 pm
In response to Pomf123
Pomf123 wrote:
Unsure if this is related but apparently changing an atom's icon from a DMI to a gif at runtime is causing crashes.

There's a .gif fix already in the can, which I think is the same issue you're talking about. I think that's not related at all to this stack overflow, though.
May 15 2016, 1:21 pm
 
(11b8.d04): Access violation - code c0000005 (!!! second chance !!!)
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files (x86)\BYOND\bin\byondcore.dll - 
eax=000001e0 ebx=000000a0 ecx=00000000 edx=000000a7 esi=00aed7b0 edi=00000000
eip=677647cd esp=00aed6c4 ebp=00aed784 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
byondcore!DMIcon::widthInTiles+0x112d:
677647cd 8901            mov     dword ptr [ecx],eax  ds:002b:00000000=????????

this helpful?
May 16 2016, 3:06 pm
Nope, crash info from widthInTiles() isn't helpful without a stack trace. The only way for that routine to crash is when the icon pointer is invalid.
May 19 2016, 3:10 pm
 
STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
00aed784 67759590 672ae100 00000000 00000000 byondcore!DMIcon::widthInTiles+0x112d
00aed7d8 677bbf99 672ae100 00000005 672ae100 byondcore!getIconDirs+0xe0
00aed7fc 677bc3d8 00000001 00000001 3ba88614 byondcore!DMTextPrinter::SetTitleEnd+0xbb99
00aed814 677bb201 458191b4 cd6f2744 00000000 byondcore!DMTextPrinter::SetTitleEnd+0xbfd8
00aed888 6783b716 00020b5a 0000148d 00aed001 byondcore!DMTextPrinter::SetTitleEnd+0xae01
00aed904 67846bfb 0001c201 0001c258 0001c201 byondcore!ServerWorldConnectionTest+0x48646
00aeddb4 67845b6c 0000000d 00aee200 0000000d byondcore!ServerWorldConnectionTest+0x53b2b
00aedde4 6783ee3f 0000000d cd6f1d88 5734b4d5 byondcore!ServerWorldConnectionTest+0x52a9c
00aee244 6786acd3 679d0240 2dc83e40 00000000 byondcore!ServerWorldConnectionTest+0x4bd6f
00aee25c 678a41ba 00000003 00000000 00aee640 byondcore!ServerWorldConnectionTest+0x77c03
00aee290 00e97562 00006140 00aee368 674f540a byondcore!TimeLib::SystemAlarm+0x10a
00aee29c 674f540a 00006140 00000000 cda1c5f8 dreamdaemon+0x17562
00aee368 674f50ca 000007ea 00006140 00000000 mfc120!CWnd::OnWndMsg+0x31d
00aee388 674f36ad 000007ea 00006140 00000000 mfc120!CWnd::WindowProc+0x22
00aee3f8 674f38cf 00aee640 0022055e 000007ea mfc120!AfxCallWndProc+0x99
00aee418 673f3a36 0022055e 000007ea 00006140 mfc120!AfxWndProc+0x34
00aee454 76438e71 0022055e 000007ea 00006140 mfc120!AfxWndProcBase+0x34
00aee480 764390d1 673f3a02 0022055e 000007ea USER32!_InternalCallWinProc+0x2b
00aee514 7643a62a 673f3a02 00000000 000007ea USER32!UserCallWinProcCheckWow+0x18e
00aee588 7644c0b0 00aee5c4 674e2d8c 00d49f08 USER32!DispatchMessageWorker+0x473
00aee590 674e2d8c 00d49f08 00000000 00aee640 USER32!DispatchMessageA+0x10
00aee5a0 674f7f80 00000004 00aee640 00000001 mfc120!AfxInternalPumpMessage+0x3e
00aee5c4 6749a745 00000004 00000000 00aee640 mfc120!CWnd::RunModalLoop+0xc6
00aee5dc 6749a9c8 00eb685c 00000000 00e80000 mfc120!CWnd::CreateRunDlgIndirect+0x3e
00aee630 00e93232 aa1e958d 00ea9ff8 00ea1178 mfc120!CDialog::DoModal+0x109
00aefc50 67506300 00000000 00d330fb 0000000a dreamdaemon+0x13232
00aefc64 00e99b8e 00e80000 00000000 00d330fb mfc120!AfxWinMain+0x47
00aefcb0 76217c04 7eabf000 76217be0 dcc40033 dreamdaemon+0x19b8e
00aefcc4 774eab8f 7eabf000 ddad419f 00000000 KERNEL32!BaseThreadInitThunk+0x24
00aefd0c 774eab5a ffffffff 774cffda 00000000 ntdll!__RtlUserThreadStart+0x2f
00aefd1c 00000000 00e99a5f 7eabf000 00000000 ntdll!_RtlUserThreadStart+0x1b
May 19 2016, 3:26 pm
Yeah, that's the .gif crasher that's already been fixed. This bug was addressed in another report. You need to upgrade to 510.1344.

Your stack overflow case remains an unknown.