ID:2512850
 
BYOND Version:512
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 77.0.3865.90
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Descriptive Problem Summary:
I only play SS13 and a few servers for which the majority of players have no issues on and recently I've been experiencing very consistent crashes across several servers. Just out of no where. For no particular reason I can discern. It simply up and says it stopped working.

There is however a little unusual things going on as well. Certain terminals ingame won't load after the first time, and even the first time the menu is blank.
And there's an unusual amount of downloading of assets randomly during gameplay when everything should already be downloaded and there's nothing new to download in the first place.

Numbered Steps to Reproduce Problem:
Just wait for it to crash.

Does the problem occur:
Every time? Or how often?
I'd say I can gaurantee a crash every hour at least, more or less sometimes.
In other games?
Just SS13
In other user accounts?
Yes.
On other computers?
Don't have a spare to test with, but i know for a fact there's some people with the *exact* same issues as I, confirmed by an admin on one of the servers.


I'll post a few logs from event viewer for the crashes here:


1. Faulting application name: dreamseeker.exe, version: 5.0.512.1485, time stamp: 0x5d83cb90
Faulting module name: byondcore.dll, version: 5.0.512.1485, time stamp: 0x5d83cb1b
Exception code: 0xc0000005
Fault offset: 0x000722c2
Faulting process id: 0x5a4
Faulting application start time: 0x01d576474791576e
Faulting application path: C:\Users\MickDick\Desktop\byond 2\byond\bin\dreamseeker.exe
Faulting module path: C:\Users\MickDick\Desktop\byond 2\byond\bin\byondcore.dll
Report Id: 4434d0ed-e23d-11e9-b45b-2a1b4c3d6e5f

- dreamseeker crash details from client:
Problem signature:
Problem Event Name: APPCRASH
Application Name: dreamseeker.exe
Application Version: 5.0.512.1485
Application Timestamp: 5d83cb90
Fault Module Name: byondcore.dll
Fault Module Version: 5.0.512.1485
Fault Module Timestamp: 5d83cb1b
Exception Code: c0000005
Exception Offset: 000722c2
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789


2. Faulting application name: dreamseeker.exe, version: 5.0.512.1485, time stamp: 0x5d83cb90
Faulting module name: byondcore.dll, version: 5.0.512.1485, time stamp: 0x5d83cb1b
Exception code: 0xc0000005
Fault offset: 0x00073685
Faulting process id: 0x83c
Faulting application start time: 0x01d576421fdb6719
Faulting application path: C:\Users\MickDick\Desktop\byond 2\byond\bin\dreamseeker.exe
Faulting module path: C:\Users\MickDick\Desktop\byond 2\byond\bin\byondcore.dll
Report Id: 30d02edc-e236-11e9-b45b-2a1b4c3d6e5f


3. Faulting application name: dreamseeker.exe, version: 5.0.512.1485, time stamp: 0x5d83cb90
Faulting module name: byondcore.dll, version: 5.0.512.1485, time stamp: 0x5d83cb1b
Exception code: 0xc0000005
Fault offset: 0x00073685
Faulting process id: 0x1430
Faulting application start time: 0x01d57654435dab11
Faulting application path: C:\Users\MickDick\Desktop\byond 2\byond\bin\dreamseeker.exe
Faulting module path: C:\Users\MickDick\Desktop\byond 2\byond\bin\byondcore.dll
Report Id: bf532cea-e256-11e9-b45b-2a1b4c3d6e5f

I can get more if needed.
That first crash points to the destructor for an icon, so some heap corruption has happened, but unfortunately the crash report you have doesn't catch that sort of thing. (The second crash is very similar, so basically the same deal.) It might be more likely to happen if Dream Seeker runs out of memory, which happens at a little under 2 GB.
I've been monitoring Dream Seeker's ram usage for a couple days now and not once has it gone even past 600 MB. So it's not running out of memory.

What do you recommend I do to get the necessary information to you?
About the only way to move forward is to find a way to reproduce this. A minidump might possibly help if I can trace the stack back, just to see if it provides any clues.
Okay. That took longer than expected as I was having issues trying to get a debugger working.

Here is a list of the various files the debugger has generated. Just let me know which ones you want and how you want it sent. Some are pretty big and will take time for me.

https://ibb.co/CnCBL18

oh and the debugger I used: was Debug Diagnostic Tool V2 Update 3 from microsoft.

If it's not acceptable point me to one that is.
Those dump files are way too big. I can't work with that size. You'll need to get dump files that are much smaller, no more than a few megabytes.
Alright I uploaded a zip with 5 minidumps I manually generated when the client crashed here: https://ufile.io/fuqot0dd

It's frustrating that this debugger only generates full dumps automatically when attached to a process. There is no means to only generate minidumps. I hope the manually generated ones aren't missing anything crucial.
Which BYOND build do those dumps apply to? I need the full version number.
5.0 Public
Version 512.1485

Login to reply.