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
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?
What version was that? It looks like it is somewhere around the mpeg synth (if using 4.16.00 mapfile is relevant to your version) – are you using mp3 data? If so are you using FMOD_CREATECOMPRESSEDSAMPLE or stream?
There was a change made in the latest versions that fixed seeking into an mpeg stream, tricking fmod’s decoder into thinking random data was actually an mpeg frame header, then decoding rubbish which caused this sort of problem.
Have you only had those 2 reports from the 10th to the 25th?
So, I deployed the FMOD_SYSTEM_CALLBACKTYPE_MEMORYALLOCATIONFAILED callback with FMOD 4.14.04 and my first new-version dmp is:
Unhandled exception at 0x1007b02c in armyofearth_cr_0.519_268939308_OS5.1.2600_312038801211077290.dmp: 0xC0000005: Access violation reading location 0x003789ec.
I.e. not OOM.
Can you help?
These last 2 crashes (0x1004f213 and 0x1007e0f3) are both 4.16.00 and are the only crashes I’ve had on that DLL; so it appears to be more stable than 4.14.04.
My game plays live music via a single createSound call with FMOD_CREATESTREAM | FMOD_NONBLOCKING | FMOD_SOFTWARE. This would be the only source of MP3 playback.
My next version will go out in 2-3 weeks. I’ll deploy the latest stable fmodex again and report back.
Please login first to submit.