Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Steven Zhou <steven.zhou@netint.ca>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] fftools/ffmpeg_filter: at EOF, unref frame used for FPS conversion logic
Date: Tue, 24 Jun 2025 03:09:23 +0000
Message-ID: <YT2PR01MB4701D5C77445443BBBDB78C4E378A@YT2PR01MB4701.CANPRD01.PROD.OUTLOOK.COM> (raw)

fftools/ffmpeg_filter: at EOF, unref frame used for FPS conversion logic

Ever since commit 64f3feb added `avcodec_free_context(&enc->enc_ctx);` to
`enc_free()` the encoder context is closed before filtergraph output context. 
The filtergraph output context holds a reference to last AVFrame to pass through
it for FPS conversion purposes. This is problematic for HWFrameContexts which
may rely on encoder context to free HW AVFrames. This change unrefs the AVFrame
ref held by filtergraph output context during processing of EOF frame.

Signed-off-by: Steven Zhou <steven.zhou@netint.ca>
---
 fftools/ffmpeg_filter.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/fftools/ffmpeg_filter.c b/fftools/ffmpeg_filter.c
index a0dc4c745e..cf2d016b2d 100644
--- a/fftools/ffmpeg_filter.c
+++ b/fftools/ffmpeg_filter.c
@@ -2560,8 +2560,10 @@ static int fg_output_frame(OutputFilterPriv *ofp, FilterGraphThread *fgt,
         av_frame_move_ref(frame_prev, frame);
     }
 
-    if (!frame)
+    if (!frame) {
+        av_frame_unref(frame_prev);
         return close_output(ofp, fgt);
+    }
 
     return 0;
 }
-- 
2.25.1

_______________________________________________
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".

             reply	other threads:[~2025-06-24  3:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  3:09 Steven Zhou [this message]
2025-06-24  3:33 ` Zhao Zhili
2025-06-24  4:47   ` Steven Zhou
2025-06-24  8:38     ` Zhao Zhili

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=YT2PR01MB4701D5C77445443BBBDB78C4E378A@YT2PR01MB4701.CANPRD01.PROD.OUTLOOK.COM \
    --to=steven.zhou@netint.ca \
    --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