ACRE.dll crash on mission start about acre2

[milivojm]

Hey guys. I will try and reproduce the issue without other mods and ring you back.

• I have noticed that issue on Altis
• I don't use Tobii EyeX
• My system has 8 GB RAM

[TheMagnetar]

Can this be reproduced with CBA and ACRE alone (or even with ACE3)? Also, the latest stable version is 2.4.0.942 and it requires TS version greater than 3.1

[Sniperhid]

Some questions that would help further:

• Does this issue happen with every island (map)?
• Do you use Tobii EyeX?
• As @TheMagnetar said does this occur if it is just CBA+ACRE2 running? (In which case finding out which mod combination sets it off would be useful).

[Sniperhid]

2017-02-19 12:46:19,241-{ERROR}- WRP Parsing exception: bad allocation - Just noticed this in the acre_dll.log. This seems to match the timestamp in the RPT. This would seem to indicate that ACRE is unable to allocate some necessary memory. Out of curiosity how much RAM does your system have?

[milivojm]

I can confirm that CBA and ACRE alone with basic mission setup module did not reproduce the issue.

I'm out of ideas now as, unfortunately, the mission preview with large modset crashes the game with the above error message every 2 launches. It smells on memory leak in arma3.exe (somewhere) and I suspect it breaks in acre.dll due to "out of memory" problem when acre maybe wants to malloc memory for something.

Is there anything you can do guys to help me out? Does the exception code and fault offset mean anything to you?

I have been tracking this issue for over two weeks with no luck.

[Sniperhid]

My gut feeling is that the large modpack is probably running Arma 3 towards its maximum allowed memory. Have you got a second screen to monitor how much RAM it is utilising? The maximum memory A3 can use has changed a bit between patchs you can set a max using the game startup parameter -maxMem=3071 - This may help
https://community.bistudio.com/wiki/Arma_3_Startup_Parameters

64bit Arma 3 should be coming with the next stable patch will may also help as it will also raise the limits higher.

It may not not be a max memory issue but it seems like a good place to start!

[milivojm]

It was definitely around that maximum judging by the procdump memory dump file size. Maybe I should limit the memory to lower value and prevent it to go there at all, something like 2GB?

[TheMagnetar]

I know it is not a workaround but what about trying the 64bit executables?

[ares]

Guys, could update your issue template so the mod list does not mention github users? Just wrap it into backticks or something? Thanks :-)

[jonpas]

@ares it is, as seen here. We can't stop people from removing the backticks though. ¯\_(ツ)_/¯

I'll change it to be a code block rather than each line separately though.

[milivojm]

I've set -maxMem=2047 and the problem now occurs a lot later with the complete modpack. Though why in the end it shows acre.dll I don't know.

[jonpas]

As far as I know changing -maxMem can lead into issues, that's why it's not as high by default. However since you are still getting crashes, it seems either too many mods for Arma to handle or some other mod causing issues. Would be pretty hard to find though, but if you could that would be interesting to see (would mean checking different combinations or single mods... etc).

[ares]

Thank you @jonpas

[jonpas]

I am going to close this issue, as it seems entirely memory related, more apparent on 32-bit Arma. If this still happens and ACRE2 seems to be the problem, reopen the issue.