0
0

I get a crash when destroying sounds every once in a while; it crashes inside fmodex.dll. Any ideas?

Edit: further investigation shows the crash to appear in sound->Release(). Testing now for a long time; perhaps it’s the SB Live’s audio drivers. Now testrunning on an AC97 onboard chip on a laptop.

******** REGISTERS ********
EAX=05DE1E88 EBX=0000025E ECX=060AFDA8 EDX=05E2AEB8 ESI=05DC8220
EDI=00000000 EBP=00000000 ESP=060AFFF4 EIP=00000000 FLAGS=00010202
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
FP Control=027F FP Status=5020 FP Tag=000F FP Cr0NpxState=00000000
FP ErrorOffset=0060CA98 FP ErrorSelector=0075001B
FP DataOffset=060AFD78 FP DataSelector=FFFF0023

******** EXCEPTION REASON ********
c:\sims\racer\racer.exe caused a EXCEPTION_ACCESS_VIOLATION (0xC0000005) in module c:\sims\racer\fmodex.dll at 001B:0060CA9A, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+9267 byte(s)

******** CALL STACK ********
001B:0060CA9A c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+9267 byte(s)
001B:0060D857 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+12784 byte(s)
001B:0060BBC2 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+5467 byte(s)
001B:0060BBC2 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+5467 byte(s)
001B:0060BBC2 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+5467 byte(s)
001B:0060BBC2 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+5467 byte(s)
001B:0060D5B4 c:\sims\racer\fmodex.dll, ?getUserData@System@FMOD@@QAG?AW4FMOD_RESULT@@PAPAX@Z()+12109 byte(s)
001B:00603961 c:\sims\racer\fmodex.dll
001B:00603D55 c:\sims\racer\fmodex.dll
001B:00607AF3 c:\sims\racer\fmodex.dll, ?tell@File@FMOD@@QAG?AW4FMOD_RESULT@@PAI@Z()+10941 byte(s)

  • You must to post comments
0
0

I’m not using NONBLOCKING no. From a test I did, starting/stopping for an hour or so, without problems, it might just be the audio driver; it only happens rarely (perhaps once for every 1000th release()).

I’ll see tomorrow what it does when reducing the driver to software-only.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.