Page MenuHomeFeedback Tracker
Create Task
Maniphest T123955

64-bit client crash in MP during mission loading (0xC0000005 - STATUS_ACCESS_VIOLATION)
Closed, ResolvedPublic
Actions

Description

In game version 1.68(.140.908), I am experiencing semi-consistent client crashes during mission loading on multiplayer servers.

I often experience an instant crash on mission selection when client-hosting a server, and when logged in as admin and selecting a mission on a dedicated server. Sometimes this does not occur and the mission iniates flawlessly, but if another player running 64-bit joins the mission in progress they will often crash after selecting a slot in the lobby and starting to load, most commonly around the "receiving mission file" phase.

I have reproduced these crashes along with other players (running Windows 10 x64), with and without the latest performance binary, with and without addons loaded, with and without any launch parameters, on both a client-hosted and a dedicated server, with different missions and mission files & settings (description.ext, init.sqf etc). Along with the report files I have included a sample mission that I have been able to reproduce the crash with.

Details

Severity
Crash
Resolution
Open
Reproducibility
Sometimes
Operating System
Windows 7 x64
Category
General
Steps To Reproduce

Reproduction Mission:

Crash_Testing_V0-0-6.Stratis.pbo16 KBDownload

(Client-host)

  1. Launch game without addons or startup parameters.
  2. Go to the multiplayer server browser and host an internet server.
  3. Select the sample mission "Crash_Testing_V0-0-6.Stratis" (possible crash).
  4. Select a slot and load the mission (possible crash).
  5. If the game did not crash, have another player running the 64-bit client connect to the server and load in, and they will almost guaranteed crash.

(Dedicated server)

  1. Launch game without addons or startup parameters.
  2. Go to the multiplayer server browser and connect to the dedicated server.
  3. If mission isn't already loaded, log in as admin and select it (possible crash).
  4. If the game did not crash, have another player running the 64-bit client connect to the server and load in, and they will almost guaranteed crash.

Event Timeline

Gilatar created this task.Mar 22 2017, 4:39 AM
Gilatar edited Steps To Reproduce. (Show Details)Mar 22 2017, 4:42 AM
Gilatar edited Steps To Reproduce. (Show Details)
Gilatar updated the task description. (Show Details)Mar 22 2017, 4:46 AM
Gilatar updated the task description. (Show Details)Mar 22 2017, 4:49 AM
Gilatar updated the task description. (Show Details)
Miller89 added a subscriber: Miller89.Mar 22 2017, 4:52 AM

I have the same issue and can reproduce it with the information described above.

GhostOps added a subscriber: GhostOps.Mar 24 2017, 8:13 AM

I also have the issue and can reproduce it on 64bit Windows 10.

Crabostabo added a subscriber: Crabostabo.Mar 24 2017, 3:20 PM

same i have been having this issue for the past few days non stop.

ArmaReport_Log_20170324T140424_Josh.zip7 MBDownload

Gilatar added a comment.EditedMar 24 2017, 8:13 PM

Tried the latest performance binary (V5 1.68.141067), but the crashing seems to persist. It is particularly consistent when I attempt to client-host a server as decribed in the inital post.

Gilatar updated the task description. (Show Details)Mar 25 2017, 8:15 PM
Pi closed this task as Resolved.Jun 9 2021, 8:14 AM
Pi claimed this task.
Pi added a subscriber: Pi.

Closing due to age

© Bohemia Interactive a.s. Bohemia Interactive® is a registered trademark of Bohemia Interactive a.s. All rights reserved. · Privacy Policy · Terms and Conditions