Page MenuHomeFeedback Tracker

Mod CBA Interaction with Eden causes crash
Closed, ResolvedPublic


I have been looking into a crash of the editor that occurs at times trying to preview the mission for the second time, or when trying to exit the editor. Have tracked this down to CBA (I am running version

Will be reporting this issue to CBA also, but I do feel that there is a issue within the Editor that needs to be addressed to better handle this.

The signature for this crash does appear to be these two event lines:

0:01:45 Warning Message: '/' is not a class ('Extended_PostInit_EventHandlers' accessed)
0:01:45 Warning Message: '/' is not a class ('Extended_InitPost_EventHandlers' accessed)

A dialog popup also occurs upon exit of a preview of the mission stating one of the above messages.

Without CBA running these events are not seen, and the editor does not crash.

Could the attached dmp be reviewed please?
{F27396} {F27397}


Legacy ID
Not Fixable
Eden Editor
Additional Information

Don't have your sym files so this can only go so far.

0:000> ||
. 0 User mini dump: arma3_2015-11-17_23-59-59.mdmp

0:000> .ecxr
eax=00005b83 ebx=00000001 ecx=4cf83a7c edx=4c61f4c0 esi=07da3038 edi=00000000
eip=011a48e5 esp=0091f278 ebp=26bafee8 iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
arma3!simul::math::Noise3D::`default constructor closure'+0xa85:
011a48e5 ff5008 call dword ptr [eax+8] ds:002b:00005b8b=????????

0:000> kb

  • Stack trace for last set context - .thread/.cxr resets it

ChildEBP RetAddr Args to Child

WARNING: Stack unwind information not available. Following frames may be wrong. 0091f278 0127e6fa 00000001 01f52920 3f7950e8 arma3!simul::math::Noise3D::`default constructor closure'+0xa85 0091f280 01f52920 3f7950e8 3f7950e8 10023020 arma3!simul::clouds::CellularCloudNode::NeedsRelight+0x1e33a 0091f29c 0128852a 00000000 00000002 26bafedc arma3!simul::clouds::CellularCloudGrid::GetGridHeight+0x119c0 00000000 00000000 00000000 00000000 00000000 arma3!simul::math::Vector::RemoveElement+0x1b5a

0:000> r eip
Last set context:

011a48d8 8b4e0c mov ecx,dword ptr [esi+0Ch]
011a48db 85c9 test ecx,ecx
011a48dd 7409 je arma3!simul::math::Noise3D::`default constructor closure'+0xa88 (011a48e8)
011a48df 8b4110 mov eax,dword ptr [ecx+10h]
011a48e2 83c110 add ecx,10h
011a48e5 ff5008 call dword ptr [eax+8]

So you are trying to use eax+8 as a pointer but due to its value that's not going to work:

0:000> r eax
Last set context:
0:000> dd eax+8 L1
00005b8b ????????

This value came from ecx+10, and we can see that:

0:000> dd ecx
4cf83a7c 00005b83 00005bc4 00006007 00006061
4cf83a8c 000060c2 00006124 000063a7 000064c4

0:000> dd ecx-10 L1
4cf83a6c 000025e7

0:000> r esi
Last set context:

0:000> dd esi+0c L1
07da3044 4cf83a6c

Event Timeline

Bohemia edited Additional Information. (Show Details)Nov 18 2015, 6:32 AM
Bohemia set Category to Eden Editor.
Bohemia set Reproducibility to Always.
Bohemia set Severity to None.
Bohemia set Resolution to Not Fixable.
Bohemia set Legacy ID to 1184003960.May 8 2016, 1:06 PM
Bohemia edited a custom field.
Adam added a comment.Nov 18 2015, 9:00 AM

Hey, the bidmp file is missing could you please attach it? It is gonna have the same name as the .RPT and .MDMP files you have attached. Thanks.

Bohemia added a subscriber: Bohemia.May 8 2016, 1:06 PM

Missed putting it in the zip, added thanks Adam. The CBA bug I logged also is:

Adam added a comment.Nov 18 2015, 2:16 PM

Hello, i was unfortunately unable to reproduce the crash. Could you please provide more info? (such as: What version of CBA Are you using etc.)

Thanks for trying Adam, let me try and help out more.

It does appear to be somewhat random on how it wants to crash, but I can always make it crash :)

Did just repro twice with the new version of DevBranch: Version: 1.55.133399, but it may take you a few attempts.

Steps to repro:

  1. Loaded Stratis in 3d editor
  2. loaded Test_3d
  3. Hit Play Scenario
  4. Hit Return to Editor
  5. Crash

Attempt before:

  1. Loaded Stratis in 3d editor
  2. Loaded Test_3d
  3. Hit Play Scenario
  4. Hit Return to Editor
  5. Press Ok on msg box
  6. Hit Play Scenario
  7. Crash

CBA Version:

Please find attached the sample mission I used that simply has a single unit.

Probable cause of the error messages seems to be that missionConfigFile doesn't always exist when exiting from in-game back to threeden editor.

eg isClass missionConfigFile = false

But handling this doesn't seem to fix crash.

Important reproduction step is that this has to be a saved mission.

Problem seems to be caused by saving missionConfigFile in an array during preInit.
Crash can be reproduced with vanilla + a mod with just

class CfgFunctions {

class PABST {
    class test {
        class crashGAme {
            file = "pabst_test\preInit.sqf";
            preInit = 1;


which does

diag_log text "PABST PRE_INIT";
x3 = [missionConfigFile];
diag_log text "PABST saved missionConfigFile in x3";

Nice job of debug work PabstMirror thanks :) all the mods I used require cba or were simply map packs.

Sounds like the exact problem I am having. It doesn't make the editor completely useless, but if I want to test the mission more than once then Arma has to be restarted. Hopefully it gets fixed soon!

Adam added a comment.Nov 20 2015, 10:13 AM

Hey, we have analyzed the dump files. Unfortunately the issue is in CBA and we cannot do anything about that. the best bet would be to report the issue to the CBA Team.

Hi Adam, really don't agree with that call. The note above from PabstMirror is from a member of the CBA mod community. Within his note he has outlined to you a very simple section of code that is all that's required to reproduce this issue.

Can this please be reviewed again, as you are going to frustrate many of your community that support your game if they issue get a beyond dev branch.

And just so it's understood my point Adam, I have over 500 hours logged into Arma 3 and more then half that time has been in the editor making content for my group. This is the first bug where I have considered it's no longer worth my time. It's that impacting to have the client constantly crash. I don't know if this has any impact but it's the community's support that keeps driving the game and it's expansions.

Just nothing this here in case people search here for the problem:

The problem has been fixed in CBA 2.2.0 and we hope to release the updated CBA before 1.54 goes stable.