0
0

Hi!

When I try to open a WMA file with FMOD EX 4.01.06, my Visual Studio.net 2003 trows various access violations… but the file is loaded and i can play an realize all operations…

CreateStream returns FMOD_OK and i can use these file with total normality.

I tried with your CreateStream example and i recive the same access violations :

First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7364 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7db6 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7db6 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c8779 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7364 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7364 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c8779 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7364 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c8779 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c8779 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7db6 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9fb2 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c9324 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.
First-chance exception at 0x086c7db6 in playstream.exe: 0xC0000005: Access violation writing location 0x00000000.

Thanks for your time 8) .

[\DReY] 2005
http://www.ayudaysoporte.com/devildrey33/

  • You must to post comments
0
0

Those are just first chance exceptions, they don’t even necessarily have to come from FMod’s code, and they won’t cause a crash. Exceptions only cause a crash if they’re not caught (and those are).

Probably worth reporting it, but I wouldn’t worry about it. Lots of Win32 APIs throw and catch those things!

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.