Page MenuHomeFeedback Tracker

DS crash on mission start IF HC is connected - C0000005 ACCESS_VIOLATION at 5C33415C
Closed, ResolvedPublic

Description

DS crashes on mission start if HC is connected at lobby screen {F24973} {F24974}

Details

Legacy ID
3269306984
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

1 - connect as admin

2 - load HC. (HC connects to correct virtual slot)

3 - start mission

4 - DS crashes

Will try to get a test mission to you.

Mission is part of a larger mod so unless I send everything to you, then I can't submit a test mission here.

On DS and clients only, there is no crashes. ONLY if HC is connected. The mission will not not crash if HC is connected after mission start (time > 0).

Additional Information

Please see crash files

Event Timeline

DasAttorney edited Additional Information. (Show Details)
DasAttorney set Category to Game Crash.
DasAttorney set Reproducibility to Always.
DasAttorney set Severity to None.
DasAttorney set Resolution to Fixed.
DasAttorney set Legacy ID to 3269306984.May 7 2016, 7:37 PM
DasAttorney edited a custom field.

Could you please upload a repro mission?

The changes you made on Friday (build 127815) seemed to have fixed crash on mission init, but the crash report I sent in #21178 is still present.

However, I read your note on that ticket that it would be fixed in upcoming build #127818 so I was waiting for that to go live and will check again for this ticket and that one.

If no change, then I’ll upload a repro.

Hi,

I just tried the update and I can't even run the mission on a DS now without the client crashing (HC is not connected).

I deliberately didn't change anything over the weekend so that I could check your changes.

I will need to go and double check my code just to make sure there isn't anything there causing this (I have done that already, but you never know).

I don't know what to do here though - I'll set up a new ticket with client crash files. Merge it in here if you need to.

At the moment though, I can't even run the mission to do a repro for the HC issues.

Hello,
is it better now? We do not have any instability reports on current dev build.

Hi,

It's not any better - client still crashes when DS spawns in units.

I opened a new ticket and put the client crash files there:

http://feedback.arma3.com/view.php?id=21296

I might go back to Stable and check everything works OK.

I just checked Stable and I don't get any crashes on DS or client (HC not tested as not in Stable yet)

Could you please upload your repro mission? We would use it for internal analysis, there was something interesting in your crashdumps. Thank you a lot.

Hi, PM'd you about test mission.

Thank you,
it should be fixed in rev. 127989. Most probably it will be in 1.36, not 1.34.
Could you please try it on Steam Dev once the version is higher than 127989? Thank you a lot.

Hi, no dice I'm afraid.

Now the DS is crashing when connecting player either enters or gets past player selection screen.

MDMP describes it as "The thread tried to read or write to a virtual address for which it does not have the appropriate access"

I've uploaded 3 sets of crash files for you. Mission should be the same as the one I sent you.

I'm on 127992. Verified files as well.

7z file icon crash.7z [^] (630,978 bytes) 2014-10-30 16:11

Update:

I doubled the RAM on the server to 2048. It's now working ok and doesn't crash out.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.