From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Zhao Zhili <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] avformat/movenc_ttml: fix memleaks (PR #20586) Date: Tue, 23 Sep 2025 14:22:44 -0000 Message-ID: <175863736472.25.7459974248998340640@463a07221176> (raw) PR #20586 opened by Zhao Zhili (quink) URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20586 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20586.patch Memory leaks can happen on normal case when break from while loop early, and it can happen on error path with goto cleanup. The two fate failures mov-mp4-ttml-stpp and mov-mp4-ttml-dfxp are the first case. >From 278fa8c69d07a4519669c851f0a51a0695761983 Mon Sep 17 00:00:00 2001 From: Zhao Zhili <zhilizhao@tencent.com> Date: Tue, 23 Sep 2025 22:08:02 +0800 Subject: [PATCH] avformat/movenc_ttml: fix memleaks Memory leaks can happen on normal case when break from while loop early, and it can happen on error path with goto cleanup. The two fate failures mov-mp4-ttml-stpp and mov-mp4-ttml-dfxp are the first case. --- libavformat/movenc_ttml.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libavformat/movenc_ttml.c b/libavformat/movenc_ttml.c index c5232e589c..ff09c14fa2 100644 --- a/libavformat/movenc_ttml.c +++ b/libavformat/movenc_ttml.c @@ -140,7 +140,7 @@ static int mov_write_ttml_document_from_queue(AVFormatContext *s, } else if (pkt->pts >= end_ts) { // starts after this fragment, put back to original queue ret = avpriv_packet_list_put(&track->squashed_packet_queue, - pkt, av_packet_ref, + pkt, NULL, FF_PACKETLIST_FLAG_PREPEND); if (ret < 0) goto cleanup; @@ -215,6 +215,7 @@ static int mov_write_ttml_document_from_queue(AVFormatContext *s, ret = 0; cleanup: + av_packet_unref(pkt); while (!avpriv_packet_list_get(&back_to_queue_list, pkt)) { ret = avpriv_packet_list_put(&track->squashed_packet_queue, pkt, av_packet_ref, -- 2.49.1 _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-09-23 14:23 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=175863736472.25.7459974248998340640@463a07221176 \ --to=ffmpeg-devel@ffmpeg.org \ --cc=code@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 http://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/ http://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