[matroska-devel] Re: Memory leaks in libmatroska partially fixed

Steve Lhomme steve.lhomme at free.fr
Mon Feb 24 23:28:10 CET 2003


Cyrius wrote:
> lol
> Well the problem is due to the fact that currently
> almost none of the Ebml elements is freed in the
> library (robUx4 will add some nice ways to do this
> later).
> However to try save some memory he already added a
> method to free allocated frames in the KaxBlock
> object. What he forgot is that when writing/reading
> with this element he copies all the data in a linear
> buffer (frames by themselves are stored in a list of
> buffers) that is used by the EbmlBinary (base class of
> KaxBlock), and of course this buffer wasn't freed ;)
> 
> Unfortunately I don't think it would be a good idea to
> commit this now because I had to add some functions (a
> way to free children in EbmlMaster, default destructor
> in some classes to free allocated memory, ...) which
> would conflict with the freeing elements that robUx4
> will add.

This is now fixed/cleaned in CVS. Tested with and without lacing :)

http://www.matroska.org



More information about the Matroska-devel mailing list