Descriptive Problem Summary:
Dreamseeker crashes during gameplay, seemingly at random. Game is Space Station 13 (/vg/station fork).
Users began to report this issue, so I attached a debugger (VS2010) to DreamSeeker and joined. After about 30 minutes, I crashed, with the attached dump and stack information.
Stacktrace: http://hastebin.com/raw/ewemabokot
Disassembly: http://hastebin.com/raw/huhomofobu
VS2010 Minidump: Contact me privately, as it contains heap information.
Numbered Steps to Reproduce Problem:
Unknown, observed occurring when idling, joining, or moving.
Code Snippet (if applicable) to Reproduce Problem: N/A
Expected Results:
N/A
Actual Results:
N/A
Does the problem occur:
Every time? Or how often?
Every few hours, but when it starts, it continues occurring until the server restarts.
In other games?
Likely.
In other user accounts?
Yes, other users have reported crashing at the same time.
On other computers?
Yes.
When does the problem NOT occur? Conditions for triggering this crash are unknown. We SUSPECT that it may be related to icon/asset transfer, as it seems to occur when moving into a certain areas. However, given the lack of symbols or even logs, we are not certain of much beyond DS crashing to desktop.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? 509.1309 does not occur to be suffering these effects, but I am still gathering information from users.
Workarounds: Unknown
In addition, I am between jobs, so please contact me if you'd like help. CV and professional references available upon request.
ID:1950964
Sep 28 2015, 4:46 pm
|
|||||||||||||
| |||||||||||||
Sep 28 2015, 4:52 pm
|
|
Apologies, posted to the wrong bug forum. Should be in the stable bugs.
|
There isn't a 509.1309 right now. Which version did you not have this issue in?
|
509.1301 did exist, I think the user reported with a typo. http://www.byond.com/ forum/?forum=5&command=search&scope=local&text=resolved%3a50 9%2E1301
|
With the stack trace on this, do you have a memory offset where byondcore.dll was?
|
Not really. I'm not sure it would really do any better than what the crash offsets can get me now.
In this case I have no offset to work with on that crash report, which leaves me in the dark. However it's entirely possible that the issue in question was solved in 509. |
It'd give you crashdumps you could open in visual studio to get complete stack traces with all the symbols and whatnot.
|
But that'd also entail getting a snapshot of the source to use. I see some advantage to it, but it's probably not worth the hassle for me.
|