0
0

Hello!
I use C++ to implement my program, and use Purify to detect memory leaks. I get a message from purify that FMOD leaks memory in FSOUND_Stream_SetBufferSize. Is there any way to release this buffer again?
Here is the report if it hepls:
MLK: Memory leak of 128 bytes from 1 block allocated in FSOUND_Stream_SetBufferSize
Distribution of leaked blocks
128 bytes from 1 block of 128 bytes (0x03c04cc8)
Allocation location
malloc [MSVCRT.dll]
FSOUND_Stream_SetBufferSize [fmod.dll]
FSOUND_Stream_SetBufferSize [fmod.dll]
RtlCharToInteger [ntdll.dll]
RtlInitializeBitMap [ntdll.dll]
CsrClientConnectToServer [ntdll.dll]
KiUserApcDispatcher [ntdll.dll]

  • You must to post comments
0
0

The GetMemoryStats() function reports 0 memory allocated after shutting down FMOD. I am begining to suspect that the problem comes from Directsound. Does the GetMemoryStats() only report FMOD mem usage or does it also take into acount that which is allocated by Directsound?

The reason why I suspect Directsound is these two error messages:

DSOUND: Error: Unable to find a topology node supporting the requested property

and a little later:
DSOUND: Error: Process 0x000004C8 leaked 1 secondary buffers

I have yet to find an explanation for the first error message in the DirectX SDK documentation. I’ll keep looking though.

But what I find really strange is that I don’t use the streaming functions at all, and yet Purifier reports this as a leak.

  • You must to post comments
0
0

I’m using DirectX 8.1. If you’re right then the problem lies with DSound and not FMOD. thanks for the info.

  • You must to post comments
0
0

I’m using FMOD 3.5.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.