Title says it all.
I can't figure out whether it's down to any of the mods or basegame.
Description
Description
Details
Details
- Severity
- Crash
- Resolution
- Fixed
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- 19043.1288
- Category
- Game Crash
Steps To Reproduce
- Load either CUP Weapons or RHS AFRF. CBA is optional, crash occurs whether it's loaded or not. CBA is only useful for buttons in this example.
- Make a mission or load into the virtual arsenal (just get access to the debug console in mission).
- Execute this code.
- Select the 'AK_762x39' category when using CUP Weapons, 'AK_545x39' when using RHS AFRF.
- Select one or multiple entries (magazines) in the 2nd listbox using shift. You must just shift click once, so you get it like in the picture.
- Select the 'AK_545x39' category when using CUP Weapons,, 'AK_762x39' when using RHS AFRF.
- Game crashes to desktop.
Additional Information
If you follow the logs I made, it crashes when it tries to clear.
I have tried to workaround the problem by using 'lbDelete' on every entry in the listbox (see commented out code), but it only pushes the problem further down the line:
When trying to add stuff back into the listbox after having removed everything, it crashes.
Arma version is 2.06 profiling branch, latest release.
Picture that I forgot to include.
Event Timeline
Comment Actions
cma_x64AVX2!cma_x64AVX2 [fail:0]
crash is in your custom cma_x64AVX2 memory allocator, try not using that, that will probably fix it.
Also get rid of your -maxvram=6000 start parameter, thats nonsense.
Comment Actions
I have removed the memory allocator and set it to default, removing the maxvram parameter aswell - but to no avail, still crashes at the exact same spot.
Disabled Large-page Support too, but also the same result:
Comment Actions
No, as I figured it was mod independent. I have managed to reproduce it just now with only NIArms and CBA loaded.
I had a friend try to reproduce it with RHS: First time it crashed for him, then it didn't after that.
EDIT:
I forgot to mention that I managed to reproduce this bug on a different computer with the 2.04 legacy branch and the 2.06 stable branch.
Comment Actions
I forgot to mention that I managed to reproduce this bug on a different computer with the 2.04 legacy branch and the 2.06 stable branch.
Could you please provide a repro with no mods loaded. The mods might have lb event handlers set which could conflict with lbClear and thus cause crash. Not much we can do about that. However if the crash happens in vanilla content, we can investigate the cause more thoroughly. Thanks
Comment Actions
I couldn't get it to crash when there were only a few items in the list (say up to 20 or 30). But when there is more than a certain amount, it crashes.
I added 3x more entries to the list (see here) which made it crash consistently on my end.
Comment Actions
Tested on Profiling build 2.06.148478
Tested the script with only CBA and CUP weapons loaded, had no crashes or freezing while preforming the repro.
Can you test if the issue persists on profiling for you?
Comment Actions
I have reproduced it on the most recent profiling branch with this code. No mods loaded whatsoever, which makes me believe it's OS/PC not playing nicely with Arma 3.
I can do it with CBA and CUP Weapons too if wanted.
Comment Actions
Thanks for the response. Which weapon did you choose to crash yourself with, in your test without mods?
I want to see if I'm able to reproduce it on my device.
Edit: https://youtu.be/Q5FTMVSJJN0 this is my repro attempt on Profiling. Am I doing the same as what causes your crash?
Comment Actions
As far as I have been able to tell, as long as the category you choose on the far left has enough entries you will make it crash by doing what I do in the video.
Comment Actions
Hello sorry it took a while to get back to you.
I was able to repro the issue on my machine, turns out if you select the top option in the ammo menu then Shift+Click it works fine.
It seems to only crash if you Shift+Click with nothing selected.
We will see what we can do to resolve the issue.
Comment Actions
It only happens when you shift+click select the magazine without having any other selected.
When you select one magazine first, that sets the selection begin.
If you then shift+click a second magazine, thats the selection end, and it selects all between begin and end.
BUT, if you shift+click the first magazine already, you never selected a selection begin point, the begin index will be at -1. the default.
So it tries to select everything between -1 and your selected item.
That actually corrupts memory and causes the crash when the listbox goes away.
Comment Actions
As far as I can tell, this issue has been addressed, I haven't had any crashes since.
For me, this ticket can be closed.