Multiple DreamDaemon faults in 0x000fcxxx range

ID:2405066
 
Oct 13 2018, 1:58 pm
BYOND Version:512.1450
Operating System:Windows 10 Pro
Web Browser:Firefox 56.2.3
Applies to:Dream Daemon
Status: Open
Issue hasn't been assigned a status value.
Descriptive Problem Summary:
Paradise has been having inconsistent crashes every few rounds with 512. All of the faults seem to happen within the `0x000fc` range.

Fault Logs:

Faulting application name: dreamdaemon.exe, version: 5.0.512.1450, time stamp: 0x5bb300c2
Faulting module name: byondcore.dll, version: 5.0.512.1450, time stamp: 0x5bb30051
Exception code: 0xc0000005
Fault offset: 0x000fc60b
Faulting process id: 0x1d88
Faulting application start time: 0x01d4630209e11068
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 69c43a42-691d-4ded-adea-c0f75852da46
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: dreamdaemon.exe, version: 5.0.512.1450, time stamp: 0x5bb300c2
Faulting module name: byondcore.dll, version: 5.0.512.1450, time stamp: 0x5bb30051
Exception code: 0xc0000005
Fault offset: 0x000fc60b
Faulting process id: 0x16d8
Faulting application start time: 0x01d462bd339268aa
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 33687f88-21ef-4c68-afcc-e025cdab91b7
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: dreamdaemon.exe, version: 5.0.512.1450, time stamp: 0x5bb300c2
Faulting module name: byondcore.dll, version: 5.0.512.1450, time stamp: 0x5bb30051
Exception code: 0xc0000005
Fault offset: 0x000fc4c1
Faulting process id: 0x8a4
Faulting application start time: 0x01d46163c6a569f6
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 8fc98340-77a4-4b7c-998f-4ba679e66903
Faulting package full name:
Faulting package-relative application ID:


Faulting application name: dreamdaemon.exe, version: 5.0.512.1450, time stamp: 0x5bb300c2
Faulting module name: byondcore.dll, version: 5.0.512.1450, time stamp: 0x5bb30051
Exception code: 0xc0000005
Fault offset: 0x000fc4a7
Faulting process id: 0x22d0
Faulting application start time: 0x01d460fc547ad993
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 76179d74-102f-4cb6-a790-793c0abae7cb
Faulting package full name:
Faulting package-relative application ID:


Does the problem occur:
Every time? Or how often? Every few restarts it'll crash randomly.
In other games? None known.
In other user accounts? Probably.
On other computers? We haven't been able to replicate it due to it's inconsistent nature.

When does the problem NOT occur?
Unknown.

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.)
511.1385 works flawlessly. We're not sure if any earlier 512 versions have the issue.

Workarounds:

Oct 13 2018, 9:50 pm
512.1450 is no longer current. Several issues have been fixed since that could explain your crashes. Please retest in 512.1453.
Oct 14 2018, 12:49 pm
We have had one on 1453, we just moved back from 511 about 4 hours ago and will update as more occur.

Faulting application name: dreamdaemon.exe, version: 5.0.512.1453, time stamp: 0x5bbfb45e
Faulting module name: byondcore.dll, version: 5.0.512.1453, time stamp: 0x5bbfb3ec
Exception code: 0xc0000005
Fault offset: 0x000fe2e7
Faulting process id: 0x1b3c
Faulting application start time: 0x01d463dc793202ec
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 0208b16b-7a16-48a7-acaa-673fef19b110
Faulting package full name:
Faulting package-relative application ID:
Oct 14 2018, 7:26 pm
Another one

Faulting application name: dreamdaemon.exe, version: 5.0.512.1453, time stamp: 0x5bbfb45e
Faulting module name: byondcore.dll, version: 5.0.512.1453, time stamp: 0x5bbfb3ec
Exception code: 0xc0000005
Fault offset: 0x000fe3e4
Faulting process id: 0x22c8
Faulting application start time: 0x01d46414f51698c4
Faulting application path: c:\Program Files (x86)\BYOND\bin\dreamdaemon.exe
Faulting module path: c:\Program Files (x86)\BYOND\bin\byondcore.dll
Report Id: 74117196-d189-4039-ba17-8e236060c2e0
Faulting package full name:
Faulting package-relative application ID:
Oct 14 2018, 9:08 pm
Well that's odd. Both of those crashes I'm seeing are coming from reading turf vars. A possible cause of this issue regarding unique turf counts was found and fixed in a recent build. Looks like there's still something causing turfs with bogus appearances, but unfortunately there's no way to tell where this is going wrong specifically.

Does this tend to happen after/during a reboot? Is there anything in the logs that might provide further useful information?
Oct 15 2018, 1:36 am
I seem to have a bit of the same. Mine crashes (or just freezes solid) I believe right after reboot sovon initialization, but it may be during.

Also unsure if these sre seperate issues or the same.
Oct 15 2018, 9:56 am
Okay, I think I have a working theory here. I believe something in your game might be accessing a completely uninitialized turf's data during the map resize routine. You basically have to be doing something horrendously un-kosher in turf/New() or one of its subroutines for that to happen, like trying to access data from a neighboring turf that doesn't yet properly exist, but then SS13 has always been known to push boundaries.

Anyway I've stuck a Band-Aid on the resize routine that should prevent such an issue, if indeed I have correctly identified the problem. If I'm right though, whatever init code you're running on the turfs is straight-up broken and is trying to access data from other turfs that it has no right to believe are valid.