[FFmpeg-devel] [PATCH] libavformat/mov.c memleak bugfix
Sat Jan 26 02:22:08 CET 2008
Zdenek Kabelac wrote:
> 2008/1/26, M?ns Rullg?rd <mans at mansr.com>:
>> "Zdenek Kabelac" <zdenek.kabelac at gmail.com> writes:
>>> If the avformat.h specify in the comment that only alllocated memory
>>> block could be used as a priv_data - than everything is fine and
>>> release could be done in generic stream_close code - it is that
>>> It's just not set clearly - so the priv_date might be used for
>>> unpredictable data.
>> The priv_data pointer in AVStream, which I assume you are referring
>> to, is managed by each (de)muxer. Nobody else has any business
>> touching it. That's what priv(ate) means.
> Of course - that's clear I guess for everyone this list.
> But it's upto to the (de)muxer how it will be used - and so far
> (de)muxer could use it to store anything it needs. When the pointer
> freeing will be placed into the generic close function and not into
> the codec - than I would expect this would be somewhere for the
> (de)muxer writter.
> I hope it's now much more clear...
So far av_write_trailer free priv_data for AVStream, I thought it was
more consistent to do the same for demuxers.
If people thinks every demuxer should free priv_data, Im ok, that would
just duplicate some code.
Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA
SMARTJOG S.A. http://www.smartjog.com
Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
Phone: +33 1 49966312
More information about the ffmpeg-devel