Re: Memory Leak

Hi,

> I'm implementing a MNG source filter for DirectShow. 

Great. Will this be usable by any DirectShow compatible application?
Will it have dynamic MNG as well?

> All is well,
> except for a very large (!) memory leak.  As near as I can tell,
> stepping through the code, it's allocating two frame buffers (through
> mng_clone_imageobject), but only ever releases one of them.  With the
> test content I'm using, this amounts to about a 2.5MB/s leak.  Ouch!
> 
> Am I doing anything (obviously) wrong?  I followed the docs carefully,
> but I didn't notice any way of explicitely freeing a frame.  I'm using
> libmng 1.0.6.

No, not at all. These buffers should disappear by themselves, no need for you 
to do anything special. However I seem to remember fixing this in either 1.0.7 
or 1.0.8. I'd suggest moving to 1.0.8 to see if it still exists. If it does, please 
send me the file that you're having trouble with, and I'll have a look to see if I 
can find the problem.



--
Send the message body "help" to [email protected]