[Matroska-users] about deleting KaxBlockBlob objects
minglinkao at instekdigital.com
Thu Nov 24 12:57:01 CET 2011
1. It would trigger an segmentation fault when deleting the pointer of a
(line 83 of the attached program)
2. In KaxCluster::Render() method, all KaxBlockBlob::Block objects are
pushed into a KaxCluster object.
Then those objects would be pointed by both KaxCluster and KaxBlockBlob.
3. How to include the V2 #defines? Thank you!
----- Original Message -----
Sent: Wednesday, November 23, 2011 7:05 PM
Subject: Re: [Matroska-users] about deleting KaxBlockBlob objects
> 1. You seem to have reversed the direction in the same; the "source"
> file is the directory named "new". The other way around would be
> 2. Checking for NULL before "delete pointer;" is not needed. That's in
> the C++ standard. The patch for this part of the file doesn't change
> the functionality at all.
> 3. I'm not convinced that your change is actually necessary. I use
> libmatroska as it is in mkvmerge including the V2 #defines, and
> mkvmerge doesn't have memory leaks that could be traced back to this
> part of libmatroska. Please show me a test case.
> Kind regards,
> Matroska-users mailing list
> Matroska-users at lists.matroska.org
> Read Matroska-Users on GMane:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
More information about the Matroska-users