I’m experiencing some strange behavior when using fmod with a pre-allocated memory pool. If a pool is too small, using FSOUND_Sample_Load () with FSOUND_LOADMEMORY flag fails (and FSOUND_GetError () returns FMOD_ERR_MEMORY), but some memory is allocated (according to FSOUND_GetMemoryStats () ). After a couple of more calls to FSOUND_Sample_Load () it just crashes (access violation) somewhere inside fmod.dll.
I tried using nosound and dsound drivers and I was able to reproduce this behavior with both of them.
I’m using fmod 3.74 on a W2K system.
- glook asked 13 years ago
- You must login to post comments