ID:239405
 
BYOND Version:493
Operating System:Windows Server 2003?
Web Browser:Firefox 9.0.1
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.
This any good for diagnosing a crash?
Problem signature:
Problem Event Name: APPCRASH
Application Name: dreamdaemon.exe
Application Version: 0.0.0.0
Application Timestamp: 4e8ba0c6
Fault Module Name: byondcore.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e8ba08f
Exception Code: c0000005
Exception Offset: 000c01bf
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Please don't use bug report posts for conversations. The information in this report may give us some clue as to where the process crashed in our code, which is the most important piece in resolving it.
Here is another one, from a different game being hosted on the same machine. The only difference seems to be the "Exception Offset". This game is not using pixel movement. The previous version of the game was stable, but the updates were so massive that I have no idea what could have lead to the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: dreamdaemon.exe
Application Version: 0.0.0.0
Application Timestamp: 4e8ba0c6
Fault Module Name: byondcore.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e8ba08f
Exception Code: c0000005
Exception Offset: 0010eacd
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
This second crash seems to have been due to large amounts of changes to turfs (Repeatedly changing the name and adding text overlays to display that name on a turf). Using turfs in this manner was causing various other issues as well. Changing the /turfs to /objs seems to have resolved all of the issues there.
I have traced both crashes and they appear to be completely independent, though without more info I can't rule out that some kind of corruption caused the first.

I've added a sanity check to the routine responsible for the first crash, which just concatenates two strings.

The other crash is in a routine that reads a cell from the map, so corrupted data from a turf operation would fit your theory. Unfortunately it doesn't point out the actual source of the problem, which will require more digging, but if it's just a matter of changing the name and appearance frequently it might be possible to reproduce.
The sanity check for the first issue will be in 494, but the second crash really needs a test case. I tried to reproduce this but failed. More info is needed.
Lummox JR changed status to 'Unverified'