Sbot Just Crashed
Socorro Henson
The problem happens for me when playing my dynamic mission with certain factions selected, specifically IFA3 factions. (In my mission, you select the factions you want to play with at the beginning, which are scanned from the config.) I've never had this crash playing with non-IFA3 factions.
In SP crash is frequent but on DS crash is pretty much an absolute certainty (Client or Server will crash, one or the other). So when testing this I mostly run my mission on DS, so if I come across something that helps, it will be obvious (due to lack of crash).
When reading about 0xC0000005 STATUS ACCESS VIOLATION error online I noticed someone saying when they switched from a 1920x1080 display to a 2560x1440 display, they started getting this error. My monitor is 2560x1440 (165hz capable with G-Sync, etc), so of course I normally run in this resolution. So I tried playing in 1920x1080 and crash hasn't happened yet (but I only tried that way a couple times). Playing in 1920x1080 is not a long term solution for me, as all my displays are 2560x1440, and importantly seems likely people playing my mission in 2560x1440 with IFA3 factions are likely getting these crashes too (considering I'm getting these crashes on at least 2 machines).
I've messed with A3 Launcher settings to see if that changes anything, with very limited success. I normally run Platform at 64-bit, but I tried running at 32-bit and this does not help (game still crashes). I have 16GB of physical system RAM and 8GB of physical VRAM. If I set Memory Allocator to "Windows allocator (system)", System Memory Limit to 10240, Video Memory Limit to 8192, and enabled Large-page Support, (and play on fresh PC boot in non-windowed mode and never alt-tabbing out of the game as precautions), this seems to help and I can usually get an entire 2560x1440 playthrough done on DS (which is pretty astounding at this point). But here's the kicker: On the subsequent DS playthough (played directly afterwards without leaving game), it crashes with 0xC0000005 STATUS ACCESS VIOLATION every time (not right away, but much sooner than normal).
During my mission development, I encountered 100s, perhaps over 1000 difficult issues, some of them complete and utter brain-benders. Through force of will and persistence, I solved them all (or at least understood and mitigated them). This issue is different (as it's a generic memory error), and has me totally flummoxed. (Plus with this, it's hard to test various remedies b/c basically you have to play mission all the way though and win which takes an hour each and every time, to know if each new remedy worked or not.)
4. I'd like to disable IFA3 scripts, to see what the culprit is (my code vs IFA3 code vs something else). Any way to do this? Even if it's hard and/or would involve me creating a giant test addon, I'm game. ?
Good deal, I will disable those and give it a go. Only thing is... I took a quick look though and I don't have "ww2_core_c_eventhandlers.pbo", either in @IFA3_AIO_LITE\addons or @IFA3_LITE\addons. In both those folders, the files present skip from "ww2_core_c_ca_cutsceneanimations_c.pbo" to "ww2_core_c_i44_animation_c.pbo". In fact, did a search within File Explorer (in both dirs) on "eventhandler" and it comes back with "No items match your search". Should that file be in there?
Good deal. Yes, I've come to this conclusion as well. The crash only happens when playing with IFA3 vehicles. Thankfully, it's super repeatable when playing my mission though. We should be able to get to the bottom of this!
For me, it happens on all 4 PCs I have access to (my 3 PCs plus my dad's), and all these PCs have updated drivers (inc video, sound, chipset, etc). (Even re-installed Windows, Steam, and A3 on one of these machines and crash still happens. And btw - All these PCs have unique hardware, as I built each one years apart.) Game crashes virtually every time, whether I'm playing in SP, HS, or DS. In MP games, sometimes it's a client (or more than one clients crashing closely together), and sometimes it's the server. Often the sound freaks out (1980s modem-style) or goes out completely shortly before the crash. Only crashes when I have IFA3 US armored vehicles selected.
2. Create an addon that replaces these cannon sounds with vanilla sounds. Play my mission and see if it crashes. @.kju Would you kindly point me to which addon I should look in to modify/eliminate these sounds?
@Dedmen and @Dwarden Thanks for looking into this. @Dwarden Per your PM request, I made it crash using the Profiling Branch (1.94.145986) and uploaded those crash files too, and sent you the link (some time ago). Curious what you guys found?
I'm 100% sure there is a bug to be found/fixed here. Really hoping we can solve it (because it's greatly affecting my game experience atm, starting to moderately sap my A3 creativity, etc), thanks! ?
Okay, I have nothing interesting to add here just a confirmation that it happened for us once again. (I have no video that shows it...at least non that is not a meme video)
In one mission we used some tanks (two different once, can't remember which) and we had two people crashing. I did not, however I and one of those that crashed had a trip down memory lane as well by listening to modem sounds. (Though I can imagine that the cause might not have been IFA but JSRS (Happened before the recent JSRS updates) Dunno if OP used JSRS aswell)
So just saying that we had this issue aswell, about 2 or 3 month ago.
Many Greetings
Moony
In one mission we used some tanks (two different once, can't remember which) and we had two people crashing. I did not, however I and one of those that crashed had a trip down memory lane as well by listening to modem sounds. (Though I can imagine that the cause might not have been IFA but JSRS (Happened before the recent JSRS updates) Dunno if OP used JSRS aswell)
I'm familiar with JSRS, but I've not tried it personally. My mission however does use radioChannelCreate and customChat (both on a regular basis) to mimic sideChat and groupChat, so that IFA3 units can receive these messages too (IFA3 units being radio-less).
I added the Profiling Branch crash files to the same folder at the link I provided originally (back when Dwarden requested). Look for "Crashes_Machine_2_Profiling_1.94.145986.7z". OK, sending you the link via PM again just in case.
you binary is also 44MB big, the server binaries are all just 32MB.
The image size exactly matches arma3client_x64_performance_194_145986_v02.exe, but the checksum is still different, and why would you even run a client performance build if you are saying you are running profiling on a dedicated server...
I can't explain what's going on here, maybe you are really running arma3 client x64 perf build, even though you said it's server and prof, and you are running it from steam branch, which has exact same build numbers as the dropbox build but is somehow still different.
So I ran this on Aug 7, 2019. "RemoteDS" tells me I was running a DS game on two different machines. In this case, one machine was the client and the other was the server. (I have a number of other crash file sets I marked "LocalDS". In those cases, one machine ran both client and server.)
[Note that sometimes (not this time though), I run Client and Server both on the same machine both using same Steam account. In that case, I have to use a different Profile for each instance of the game, otherwise I get some warning or error about profiles.]
Atleast now I know which build you are using, problem is that your last crash on performance build was with a old version from steam that I cannot get anymore, I can only get the dropbox version, which is for whatever reason different despite being the exact same version number and type.
I just changed back to the "profiling - Performance Profiling Build" option, and noticed for the first time a file called "arma3profiling_x64.exe" in my Arma 3 dir. It is dated with today's date and time, indicating it was just downloaded. Is this the latest "profiling" exe and can I simply run from here? -OR- Do I really need the exe from dropbox instead? [If so will need a bit of help knowing which file to choose from dropbox and which file to (temporarily) replace & run in Arma 3 dir, so we can avoid another disconnect.] Thanks again.
(Note- I noticed that when game crashes after being launched from bat file, you don't get the windows pop-up error upon crash saying "0xC0000005 STATUS ACCESS VIOLATION". I had to look inside the rpt to verify the type of crash, which was indeed "C0000005 ACCESS_VIOLATION". Also note time of the 3 crash files matched the time of the crash.)
It tries to check whether the magazine has 0 ammo left, because then it can just delete it.
While trying to get ammo though instead of calling a function of the magazine, it jumps into invalid memory. Because something apparently bricked the address of the magazine in the meantime.
It should've jumped to 0x7FF7DA543780 but instead it ended up in 0x2EBA5788220
Total nonsense. And I don't really understand how that happens. Well I have some ideas but still doesn't make sense.
And even less sense that it really only happens with IFA3. Such a crash shouldn't be possible to be caused with config.
While retrieving the ammo of the magazine currently in the weapon, it tried to jump and execute code at the location of a string.
Seems like somehow some pointers got mixed up. I don't think I can solve this without a BI dev. Actually I think a BI dev couldn't figure this out either, without being able to reproduce by himself.
Crashed in sound processing, while Arma was doing AI processing in the meantime?
Now we have a crash, with a AI unit currently being worked with by some code, and a string containing a soundpath accidentally being used as a assembly code address.
Will chime in here since the dedicated server I have in use is occasionally crashing. Dedmen was kind to take a look into the issue back in July so I provided crash dumps from the then latest stable Arma 3 version 1.92.145639. What Dedmen found was along the lines he now typed (about the magazine stuff) in his latest reply to this thread.
Now the server is using the latest stable Arma 3 version 1.94.145977 and the (server) crashes still continue. Just for anyone's information there's been crashes on the 24th, 26th and 27th of August. Since then it's been quiet regarding crashes but that's most likely because of the fact that the server has been empty most of the time :)