I’m using valgrind to fix leaks and such in my program, but the moment I link libfmodevent.so in, I get a huge amount (48 in a test the only tries to play two events) of messages from valgrind all starting like this:
[quote:cpv18vel]==8113== Mismatched free() / delete / delete []
==8113== at 0x401D095: free (vg_replace_malloc.c:233)
==8113== by 0x49310AC: operator delete(void*) (in /usr/lib/libfmodevent.so)
After the "delete" line it seems I can see every place that calls a delete in the trace…including the stl 😕

The programs I check all run and finish normally, so I’m pretty sure I’m not doing anything wrong.
Are these message normal for programs linked against fmod? Is there any way to get rid of those messages?


  • You must to post comments

Pretty sure valgrind is just getting confused by the way FMOD handles memory internally. If there’s a way to get rid of the messages it might be in the valgrind docs? Some way to exclude certain modules maybe?


  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.