Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: ffmpeg-devel@ffmpeg.org, "Xiang, Haihao" <haihao.xiang@intel.com>
Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_encode: fix segfault
Date: Mon, 30 Jan 2023 08:55:52 +0100
Message-ID: <167506535205.4503.8778082800087432409@lain.khirnov.net> (raw)
In-Reply-To: <20230130052321.27566-1-haihao.xiang@intel.com>

Quoting Xiang, Haihao (2023-01-30 06:23:21)
> From: Haihao Xiang <haihao.xiang@intel.com>
> 
> This is a regression since commit fbdba9a1a69fe4df413d9e9df1b11db522946e75
> 
> input_image is freed in vaapi_encode_wait() however it is still used in
> commit fbdba9a1a69fe4df413d9e9df1b11db522946e75
> 
> $ ffmpeg -vaapi_device /dev/dri/renderD128 -f lavfi -i testsrc -vf
> "format=nv12,hwupload" -c:v h264_vaapi -f null -
> 
> Note input_image will be freed in vaapi_encode_free() now.
> 
> Cc: Anton Khirnov <anton@khirnov.net>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
>  libavcodec/vaapi_encode.c | 3 ---
>  1 file changed, 3 deletions(-)

Thank you, looks good.

Could swear I tested this, but apparently not :/

-- 
Anton Khirnov
_______________________________________________
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:[~2023-01-30  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30  5:23 Xiang, Haihao
2023-01-30  7:55 ` Anton Khirnov [this message]
2023-01-30 15:15   ` Xiang, Haihao
2023-01-31 13:14     ` [FFmpeg-devel] [PATCH] lavc/vaapi_encode: fix propagating durations and opaques Anton Khirnov
2023-02-01  2:59       ` Xiang, Haihao
2023-02-02  2:47         ` Xiang, Haihao

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=167506535205.4503.8778082800087432409@lain.khirnov.net \
    --to=anton@khirnov.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=haihao.xiang@intel.com \
    /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