ID:1733670
 
Resolved
Sending an invalid database datum to output could sometimes cause a crash.
BYOND Version:507
Operating System:2012
Web Browser:Firefox 31.0
Applies to:Dream Daemon
Status: Resolved (507.1270)

This issue has been resolved.
Faulting application name: dreamdaemon.exe, version: 5.0.507.1269, time stamp: 0x547fa981
Faulting module name: byondcore.dll, version: 5.0.507.1269, time stamp: 0x547fa8c6
Exception code: 0xc0000005
Fault offset: 0x0014aec0
Faulting process id: 0x2f6c
Faulting application start time: 0x01d01058d0fccf6e
Faulting application path: C:\Program Files (x86)\byond\bin\dreamdaemon.exe
Faulting module path: C:\Program Files (x86)\byond\bin\byondcore.dll
Report Id: b0e3a48e-7c4d-11e4-93fa-001e8cf19ccb
Faulting package full name:
Faulting package-relative application ID:

<dm>Faulting application name: dreamdaemon.exe, version: 5.0.507.1269, time stamp: 0x547fa981
Faulting module name: byondcore.dll, version: 5.0.507.1269, time stamp: 0x547fa8c6
Exception code: 0xc0000005
Fault offset: 0x0014aec0
Faulting process id: 0xcd8
Faulting application start time: 0x01d0112ead167cd8
Faulting application path: C:\Program Files (x86)\byond\bin\dreamdaemon.exe
Faulting module path: C:\Program Files (x86)\byond\bin\byondcore.dll
Report Id: 209127ea-7d64-11e4-93fa-001e8cf19ccb
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 73708269778, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: dreamdaemon.exe
P2: 5.0.507.1269
P3: 547fa981
P4: byondcore.dll
P5: 5.0.507.1269
P6: 547fa8c6
P7: c0000005
P8: 0014aec0
P9:
P10:

Attached files:
C:\Users\ririchiyo\AppData\Local\Temp\WEREC5F.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\ririchiyo\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_dreamdaemon.exe_f912128bc71c6950c5c2f82794194cb552db471_db8e3ee6

Analysis symbol:
Rechecking for solution: 0
Report Id: b0e3a48e-7c4d-11e4-93fa-001e8cf19ccb
Report Status: 0
Hashed bucket: 2c7fa53299df4fca25c968eeeafdca21


Heres the windows error reporting dump, http://ss13.undo.it/sekrit/ AppCrash_dreamdaemon.exe_f912128bc71c6950c5c2f82794194cb552d b471_db8e3ee6.zip
Those reports are nice and consistent, so I should be able to find the issue Monday.
My trace says this is happening when it's trying to get a name for a datum. The datum is coming up as bogus, which is odd. I'm not sure what the exact cause of this is, as there shouldn't be any way for a bogus datum reference to reach this point. However, I see a distinct lack of a sanity check in this routine, so adding that should fix the issue.
Anyway you can ping me on the pager when you have a new build up with the sanity checking added, the pager has stopped telling me when i get replies to threads.
Lummox JR resolved issue with message:
Sending an invalid database datum to output could sometimes cause a crash.