Descriptive Problem Summary:
When playing any of the few games I happen to play randomly at random points of time the Dream Seeker will random crash.
However recently a friend and myself were on Skype together while playing on the same game we both experienced this crash at the same time. No one else in the game received this crash and he as well has reported these crashes on the many games he also plays.
Numbered Steps to Reproduce Problem:
Play a game till your client crashes.. >.>
Does the problem occur:
Every time? Or how often? Varies
In other games? Yes
In other user accounts? Yes
On other computers? Yes
ID:1312442
 Jul 3 2013, 8:27 am
|
|||||||||||||
| |||||||||||||
If you can get crash details, like the module where it crashed and the offset, I can trace that. I'll need an exact build number to go with it. It would help to know which games show this problem as well.
| |
Well, I personally recall testing this in three project files, Zeta Rip Dark Apocalypse, Elemental Warfare, and my personal RundleMent, which I can't currently provide a test for. The only one I haven't reproduced the problem with is RundleMent, but that could very well be the limited time I've spent on the project outside of testing. Otherwise, I've only asked a handful of people I know if they've experienced the same issue, to which they say they've had issues on games like 'cow' something and mitidake high. Not sure what exactly causes it, but it didn't start for me until roughly a year, and and a half ago. I'll download earlier versions of BYOND to try and pinpoint when, but that could be difficult with the unpredictable way this happens, where I haven't experienced the issue since my post, where the crashes were occurring rather rapidly. I'm about to head to bed, so I can't provide much more information at the moment.
| |
I am currently running 498.1163. This issue started roughly a year ago for me as well. However I may not see the error for weeks or months at a time.
As NNAAAAHH said at the time of my post the crashes were in extreme proximity to one an other. But I have also never experienced them that badly before either. | |
Next time there is a crash, Click start, type "Event Viewer" and hit enter. Navigate to Windows Logs and finally Application.
Look through the list of errors and find the one related to your crash. Post the faulting info. Should look something like this: http://i.imgur.com/cR9JEUW.png | |
It seems the errors are faulting because of byondcore.dll?
| |
That doesn't help, you'll need to post the faulting info. Those little numbers in the report are used by the developers to figure out what went wrong.
| |
Shadowkaroth wrote:
It seems the errors are faulting because of byondcore.dll? That's good to know--it means it's something on the backend and may be traceable. I need to know the offset of the crash, and the exact BYOND build number. | |
Here's just two random ones:
Log Name: Application Source: Application Error Date: 7/3/2013 1:20:12 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: My-HP Description: Faulting application name: dreamseeker.exe, version: 4.0.499.1197, time stamp: 0x51d1edd9 Faulting module name: byondcore.dll, version: 4.0.499.1197, time stamp: 0x51d1ed83 Exception code: 0xc0000005 Fault offset: 0x00055d9a Faulting process id: 0x2830 Faulting application start time: 0x01ce7810ee4b8dda Faulting application path: C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe Faulting module path: C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll Report Id: d1513f11-e404-11e2-8e0f-d0df9ade3239 Event Xml: 1000 2 100 0x80000000000000 25185 Application My-HP dreamseeker.exe 4.0.499.1197 51d1edd9 byondcore.dll 4.0.499.1197 51d1ed83 c0000005 00055d9a 2830 01ce7810ee4b8dda C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll d1513f11-e404-11e2-8e0f-d0df9ade3239 ________________________ Log Name: Application Source: Application Error Date: 7/3/2013 1:25:58 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: My-HP Description: Faulting application name: dreamseeker.exe, version: 4.0.499.1197, time stamp: 0x51d1edd9 Faulting module name: byondcore.dll, version: 4.0.499.1197, time stamp: 0x51d1ed83 Exception code: 0xc0000005 Fault offset: 0x00055d9a Faulting process id: 0x38ec Faulting application start time: 0x01ce7812226bf79c Faulting application path: C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe Faulting module path: C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll Report Id: 9fa6be4d-e405-11e2-8e0f-d0df9ade3239 Event Xml: 1000 2 100 0x80000000000000 25189 Application My-HP dreamseeker.exe 4.0.499.1197 51d1edd9 byondcore.dll 4.0.499.1197 51d1ed83 c0000005 00055d9a 38ec 01ce7812226bf79c C:\Users\Sketh\Documents\BYOND\bin\dreamseeker.exe C:\Users\Sketh\Documents\BYOND\bin\byondcore.dll 9fa6be4d-e405-11e2-8e0f-d0df9ade3239 | |
Log Name: Application
Source: Application Error Date: 7/3/2013 12:25:57 PM Description: Faulting application dreamseeker.exe version 4.0.498.1163 time stamp 0x50e499c3 faulting module byondcore.dll version 4.0.498.1163 time stamp 0x50e49983 exception code 0xc0000005 fault offset 0x00056649 process id 0xfec application start time 0x01ce7811f8982220 | |
Why me? Is it because of how good I look?
Also, would like to know if this is verified yet; since there's another case in BYOND Help that popped up. This time is SS13 clients. http://www.byond.com/forum/?post=1330373 | |
It's still happening, the crashes they have yet to cease on the new version of BYOND or any of the previous, it's quite annoying.
| |
If you get a crash in Dream Seeker, please post details from the crash including the module that crashed and the memory offset where it happened. If you're using a newer version of Windows, you can use the event viewer as described earlier in this thread. In Windows XP, use Dr. Watson and you'll get info in its log.
These should include the version info from the crash details, but if that's not present, please be sure to provide the exact major and minor build number (e.g., 499.1200). | |
Description:
A problem caused this program to stop interacting with Windows. Problem signature: Problem Event Name: AppHangB1 Application Name: dreamseeker.exe Application Version: 4.0.498.1148 Application Timestamp: 50a4616c Hang Signature: 2cde Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: 2cde090249aef0634cc116b9aeceae61 Additional Hang Signature 2: cc8b Additional Hang Signature 3: cc8b8a7e7284ed4ce3ad944a85719bf5 Additional Hang Signature 4: 2cde Additional Hang Signature 5: 2cde090249aef0634cc116b9aeceae61 Additional Hang Signature 6: cc8b Additional Hang Signature 7: cc8b8a7e7284ed4ce3ad944a85719bf5 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 The program dreamseeker.exe version 4.0.495.1136 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: e34 Start Time: 01ce792ad5b3fed9 Termination Time: 56 Application Path: C:\Program Files (x86)\BYOND\BYOND\bin\dreamseeker.exe Report Id: 2827682d-e522-11e2-9a40-d0278867a190 | |
Is...that reporting two different version numbers?
| |
A hang is not a crash. Without some info on where it was hanging, that won't be of much use. It looks like the event viewer didn't keep track of anything relevant that I could look at.
Mind you, if you were running a game yourself and not merely joining a remote server, this could be the heap corruption problem we've been chasing in another thread. That seemed to mostly (perhaps exclusively) impact certain flavors of Linux, but in 499.1202 I ended up fixing a possible cause of heap corruption that could have impacted Windows builds as well. This was a server-based change, though. I recommend trying build 499.1202, since 498.1148 is no longer current. As for getting better details out of Windows when it closes down a hanging program, I don't know if there's anything it can do. | |
It hangs until I close it, and no I wasn't running and the game, and it does the same thing on 499, actually its worse on 499.
| |
What's the earliest version that doesn't hang?
I would also recommend installing Windows debugging tools. If you open up the debugger and then run the program, you can attach the debugger to it once it freezes and that can be used to find out where it's hanging. Without knowing that there's not a lot I can do except speculate, since the bug can't be reproduced reliably. | |
I've seen this rarely but never been able to reproduce. If I see another I'll take a look at it with a debugger.
| |
This has happened with me for some time and some times, like today, it gets really bad and crashes anywhere between thirty seconds to five minutes of game-play. Other times I can leave a game open for hours(when I forget to close things when I lay down) without issue.
Using 499.1197 currently, and the issue has been present all throughout 498. Unsure of when the last time it didn't occur like this was.