Deterministic crashes when starting certain selfmade missions from within Eden - Code 0xC0000005 - STATUS_ACCESS_VIOLATION
New, NormalPublic

Tags
Subscribers
Assigned To
None
Authored By
oldy41, Mon, Apr 17

Description

Win10 Home, Nvidia GTX970, ArmA3 Dev branch

I keep getting crashes with code 0xC0000005 - STATUS_ACCESS_VIOLATION when starting some of my own (rather simple) missions with IFA3Lite.

The crashes occur consistently when starting to play the affected missions from Eden. Usually it helps deleteing some units, but after re-adding them the mission is consistently crashing again directly at startup.

Reproducable with both 32 and 64bit dev branch builds for about 2 weeks now.
This happens with mods only, but I am still reporting since a mode with no native code should not be able to crash the game.

Details

Severity
Crash
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
Game Crash
Steps To Reproduce

Scenario 1:
Modset: CUP_Terrains-Core, CUP_Terrains, Carraigdubh

  1. Start Eden on Carraigdubh terrain
  2. Start creating a new mission
  3. Put a vanilla infantry unit on the map
  4. Preview mission -> immediate crash 0xC0000005 - STATUS_ACCESS_VIOLATION after the mission has loaded

Scenario 2:
Modset: CUP_Terrains-Core, IFA3_Objects_Lite, IFA3_Terrains_Lite, IFA3_AIO_Lite

  1. Start Eden on Altis
  2. Load specific mission
  3. Preview mission -> immediate crash 0xC0000005 - STATUS_ACCESS_VIOLATION after the mission has loaded
Additional Information

Scenario 1 always crashes on Carraigdubh, regardless of the mission.

Scenario 2 (IFA3 Lite) seems to be dependent on mission complexity. After adding a certain amount of units that mission then crashes deteministically directly at startup.

I can provide mission examples and crahs files, but where to put them?

oldy41 created this task.Mon, Apr 17, 5:28 PM

ArmaReport_Log_20170418T180336_ahe.zip

mission.sqm
Crash dump an mission for scenario 2 (IFA3 Lite) uploaded.

Add Comment