I was just stress-testing my program, and after about an hour or so I had a crash in fmodex.dll
I then ran the test again linking to the debug version fmodexl.dll and I got the same error again.
The error I got was:
Unhandled exception at 0x01248c39 in djDecks.exe: 0xC0000005: Access violation reading location 0x812abc2c
The error is in a thread with only the name ‘Win32 Thread’ at normal priority. The stack begins and ends with fmodexL.dll so it appears to be an fmod-created thread.
The fmod calls used were sound->readData and sound->seekData
They can be called from different threads, but all fmod calls are inside a critical section.
In my application I have 2 playback modes, one which reads the complete file into memory (and thus only uses readData) which I have not been able to crash for 8 hours. And another one which streams part of the data and thus also uses seekData.
I will now be testing again with 4.08.04 but I didn’t see anything in the changelog that could cause this…
I think that if the problem was on my side it would crash at the moment I called one of the functions, and not in an fmod thread right?
The output type for fmod is FMOD_OUTPUTTYPE_NOSOUND_NRT by the way.
- Adion asked 9 years ago
- You must login to post comments