ID:120220
 
BYOND Version:493
Operating System:Windows 8 Developer Preview
Web Browser:Chrome 15.0.874.92
Applies to:Dream Seeker
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.
Descriptive Problem Summary: I've recently had this issue in Feval, something keeps crashing it, however the crashes are 'random' and can't get what's causing them.

This is what it says: "Unhandled exception at 0x00406a52 in dreamseeker.exe: 0xC0000005: Access violation reading location 0x00000000"

Some information from Microsoft Visual Studio Debugger.

"Call Stack location": dreamseeker.exe!00406a52()
"Dissasembly": 00406A52 mov eax,dword ptr [edi]

Call Stack:

dreamseeker.exe!00406a52()
[Frames below may be incorrect and/or missing, no symbols loaded for dreamseeker.exe]
dreamseeker.exe!00406912()
dreamseeker.exe!00406769()
dreamseeker.exe!00409cdc()
dreamseeker.exe!004041d5()
dreamseeker.exe!00403453()
mfc42.dll!63baa868()
mfc42.dll!63baa855()
mfc42.dll!63baaa7e()
mfc42.dll!63bab515()
mfc42.dll!63bab478()
mfc42.dll!63bab815()
user32.dll!7600b093()
user32.dll!760027da()
user32.dll!7600b16d()
user32.dll!7600415f()
user32.dll!760041f5()
ntdll.dll!77876e8e()
user32.dll!75ffbda3()
mfc42.dll!63bb40a8()
mfc42.dll!63bd03d2()
mfc42.dll!63be2252()
dreamseeker.exe!00412794()


Numbered Steps to Reproduce Problem:
1.-Play Feval
2.-Wait for a random crash (Happened me when it was minimized and then maximized it).

Expected Results: Not crashing.

Actual Results: Crashes.

Does the problem occur:
Every time? Or how often? Randomly.
In other games? Haven't tryed.
In other user accounts? Haven't tryed.
On other computers? Haven't tryed.

When does the problem NOT occur? -

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.)

Workarounds: Close the Dream Seeker and run the game again.

Can you get more detailed crash info than that? The OS has given you the memory location of the crash, but not the offset within the program or (seemingly) information about which module is crashing. I can't disassemble without a correct module and offset.

Also, please be sure you're running 493.1117. If you're on the 1116 build, upgrade immediately and see if the problem goes away.
I'm running 493.1117. I'll try to get more detailed info whenever it crashes again.