0
0

Has anybody else noticed this?
I’m using the latest version of FMOD with VC++ 6, and my usage of FMOD is pretty trivial:

FSOUND_SetBufferSize(200) ;
FSOUND_SetOutput(FSOUND_OUTPUT_DSOUND) ;
FSOUND_SetDriver(0) ;
FSOUND_SetMixer(FSOUND_MIXER_AUTODETECT) ;
FSOUND_Init(44100, 32, 0) ;
m_pfssMusicStream = FSOUND_Stream_OpenFile(m_pszMusicFiles[m_ndxCurMusicFile], FSOUND_LOOP_NORMAL, 0) ;
FSOUND_Stream_Play(0, m_pfssMusicStream) ;

FSOUND_Close()

Purify also reports mem. leaks on Direct3D8… any input is appreciated…

thanks,

dm.

  • You must to post comments
0
0

Ok but FMOD doesn’t use Direct3D (it s for grafix), do you mean DirectSound3D instead ?

  • You must to post comments
0
0

Well, yeah. The DX (DSound) debug output reports lost secondary sound buffers, presumably through FMOD’s usage.

The Purify memory leak reporting is a separate issue: whether or not memory is really leaked from FMOD is the question I’d like answered… like I say, it also reports mem. leaks on standard D3D sample applications which make me suspicious of what it’s saying about FMOD…

  • You must to post comments
0
0

I got this Purify leak as well under v3.33, with exactly the same circumstances; when opening a stream.
I reported it here a few weeks ago. Purify really is quite good at detecting this stuff, but indeed, it also complains about system DLLs as well (which is not surprising actually, since we’re on Windows 😉 ).

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.