From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2] lavf/mpegenc: fix memory leak in the fifo since the new API
Date: Mon, 21 Mar 2022 22:09:52 +0100
Message-ID: <AS1PR01MB95646D936B07343CAB3691F88F169@AS1PR01MB9564.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20220318131504.18488-1-nicolas.gaullier@cji.paris>
Nicolas Gaullier:
> The older av_fifo_realloc2 implemented an auto grow that should be ported as such.
>
> This introduces a limitation in the buffer size.
> AUTO_GROW_DEFAULT_BYTES is currently 1MB which seems reasonable here.
>
> Fix regressing since ea511196a6c85eb433e10cdbecb0b2c722faf20d
>
> Signed-off-by: Nicolas Gaullier <nicolas.gaullier@cji.paris>
> ---
> libavformat/mpegenc.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/libavformat/mpegenc.c b/libavformat/mpegenc.c
> index cc47a43288..ba0b5d813a 100644
> --- a/libavformat/mpegenc.c
> +++ b/libavformat/mpegenc.c
> @@ -461,7 +461,7 @@ static av_cold int mpeg_mux_init(AVFormatContext *ctx)
> av_get_media_type_string(st->codecpar->codec_type), i);
> return AVERROR(EINVAL);
> }
> - stream->fifo = av_fifo_alloc2(16, 1, 0);
> + stream->fifo = av_fifo_alloc2(16, 1, AV_FIFO_FLAG_AUTO_GROW);
> if (!stream->fifo)
> return AVERROR(ENOMEM);
> }
> @@ -1151,7 +1151,7 @@ static int mpeg_mux_write_packet(AVFormatContext *ctx, AVPacket *pkt)
> StreamInfo *stream = st->priv_data;
> int64_t pts, dts;
> PacketDesc *pkt_desc;
> - int preload, ret;
> + int preload;
> const int is_iframe = st->codecpar->codec_type == AVMEDIA_TYPE_VIDEO &&
> (pkt->flags & AV_PKT_FLAG_KEY);
>
> @@ -1207,10 +1207,6 @@ static int mpeg_mux_write_packet(AVFormatContext *ctx, AVPacket *pkt)
> pkt_desc->unwritten_size =
> pkt_desc->size = size;
>
> - ret = av_fifo_grow2(stream->fifo, size);
> - if (ret < 0)
> - return ret;
> -
> if (s->is_dvd) {
> // min VOBU length 0.4 seconds (mpucoder)
> if (is_iframe &&
You mean an ever-growing buffer when talking about a "memory leak"?
Because I actually don't see any ordinary memory leak.
- Andreas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-03-21 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 13:15 Nicolas Gaullier
2022-03-19 14:51 ` Anton Khirnov
2022-03-21 21:09 ` Andreas Rheinhardt [this message]
2022-03-22 8:14 ` Nicolas Gaullier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AS1PR01MB95646D936B07343CAB3691F88F169@AS1PR01MB9564.eurprd01.prod.exchangelabs.com \
--to=andreas.rheinhardt@outlook.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git