My game has a mechanism to send in-the-field exceptions to me rather than to Microsoft. Received the following. No additional info known. Dump filename tells me it was Vista, flavor unknown.
FMOD VERSION: 4.14.01
Unhandled exception at 0x1007ab2d in armyofearth_cr_0.518_268938029_OS6.0.6000_589249761209361074.dmp: 0xC0000005: Access violation reading location 0x00e2b000.
Any comment from FMOD? Can you use this address?
- fundictive asked 10 years ago
Now on 4.16.04. Probably the most stable yet.
However got this user crash:
Unhandled exception at 0x10021b47 in armyofearth_cr_0.521_268573511_OS5.1.2600_228823081215831640.dmp: 0xC0000005: Access violation reading location 0x013f1000.
did the change to the latest version show any effect? We’re having some strange and seemingly random crash within the fmodex.dll as well and I’m still trying to find a way to reproduce it in order to be able to say whether the new version fixes it…
[Frames below may be incorrect and/or missing, no symbols loaded for fmodex.dll]
I am also getting random crashes in fmod recently. The sound seems to be fine, then it just crashes, i’m not sure how to debug to be honest. The dll version is : – 0.4.16.3
Some background: –
I am doing a racing engine – so i have a few wav samples that I change the frequency and volume of according to revs. I combined 2 wavs that were recorded at the RPM nearest to the current RPM. I also have tyre noise depending on the slipratio/angle of the tyre.
Hope this helps debug the problem, if i can provide any more info, please let me know.
All the best,
Unhandled exception at 0x1007aaf3 in armyofearth_cr_0.518_268937971_OS5.1.2600_350443201210392456.dmp: 0xC0000005: Access violation reading location 0x015b1000.
These are all separate computers.
Can I confirm that you are not doing non thread safe fmod calls, ie calling fmod from different threads? Overriding fmod callbacks without having threadsafe functionality in your callback code? Maybe you’re running out of memory? (system out of memory callback can catch that).
No, the game itself uses 1 thread only.
I overload the new operator and generate my own exception for failure, but haven’t seen that come up.
Can you use the addresses to determine the functions that it is crashing in?
Then you are in a better position than I – I’ve never seen it myself and wouldn’t know about the crashes except that I have a mechanism to receive crash dumps from the field.
All the callstacks I received were shallow, i.e. no application calls show.
I suggest you soak with the new version and follow up with the crash address(es) if you get any more…
According to the map file that is inside the resampler in fmod’s mixer. As this never usually happens I can only assume you’ve run out of memory due to maybe setting up a memory pool incorrectly, or you have corruption. Your other thread seems to qualify that something strange is going on in your game, fmod just doesnt crash like the ways you mention.
For the out of memory case you can catch it in the system callback like I said, or run the logging version of fmod and it will spit out a line about the error as soon as it happens.
Guess I’ll just keep posting crash addresses as they come up. Stability has improved significantly since the start of this thread though.
I’m now on fmodex v 4.16.08.
This is probably a NULL deref:
Unhandled exception at 0x1001abe8 in armyofearth_cr_0.522_268545000_OS5.1.2600_299636601218387169.dmp: 0xC0000005: Access violation reading location 0x00000000.
These crashes are happening on a small percentage of game clients; I am guessing 1-2%. Certainly I have never seen such crashes myself and no user has mentioned it. I would never know about these crashes but for the minidump upload capability – so, what if the crashes are representative?
What is the system callback you are talking about?
As for the getDriverCaps failure in my other post – the entire init code preceding that is included in the post – is it flawed?
I’ve now deployed a new version of my game with the new fmodex.dll and the first minidump is:
Unhandled exception at 0x1007e0f3 in armyofearth_cr_0.520_268951795_OS5.1.2600_22725041212993170.dmp: 0xC0000005: Access violation reading location 0x02234000.
So it appears that some crash bugs persist. May not be the same code vicinity though.
Another one today.
Unhandled exception at 0x1004f213 in armyofearth_cr_0.520_268759571_OS5.1.2600_236017561214332901.dmp: 0xC0000005: Access violation reading location 0x2ebede60.
Perhaps you FMOD guys can look up these addresses?
Please login first to submit.