From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] Fixed nvenc release dump
Date: Fri, 24 Nov 2023 13:38:16 +0100
Message-ID: <d8c5103a-509b-414a-a88b-feecb6e06170@rothenpieler.org> (raw)
In-Reply-To: <PAXPR10MB510308EA2779D5FEADEA420DEAB8A@PAXPR10MB5103.EURPRD10.PROD.OUTLOOK.COM>
I don't quite understand the commit message.
It should start with "avcodec/nvenc:" and then state what it's changing
and why.
On 24/11/2023 08:04, GOOR, Jean-Noel wrote:
> Signed-off-by: GOOR, Jean-Noël <jn.goor@evs.com>
> ---
> libavcodec/nvenc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/nvenc.c b/libavcodec/nvenc.c
> index 3c68ed3930..1f8c7e8c0e 100644
> --- a/libavcodec/nvenc.c
> +++ b/libavcodec/nvenc.c
> @@ -1860,7 +1860,7 @@ av_cold int ff_nvenc_encode_close(AVCodecContext *avctx)
> av_fifo_freep2(&ctx->unused_surface_queue);
>
> if (ctx->frame_data_array) {
> - for (i = 0; i < ctx->nb_surfaces; i++)
> + for (i = 0; i < ctx->frame_data_array_nb; i++)
Wrong indentation.
The change itself looks correct to me on first glance.
Did you find this via a leak checker?
> av_buffer_unref(&ctx->frame_data_array[i].frame_opaque_ref);
> av_freep(&ctx->frame_data_array);
> }
_______________________________________________
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:[~2023-11-24 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <75bc2482-ee76-46e0-b158-59812d9b556b.6b3277fd-9509-4eec-8a03-dcd135675389.0e59a80c-5bf2-4680-b41a-4eb1b2bdcf08@emailsignatures365.codetwo.com>
[not found] ` <75bc2482-ee76-46e0-b158-59812d9b556b.f81fd677-2c20-4d59-96be-51794e3dd064.4698ae07-9841-4b8f-9f5a-42c776da289f@emailsignatures365.codetwo.com>
[not found] ` <75bc2482-ee76-46e0-b158-59812d9b556b.0878c2f3-5737-4b62-9d31-5d0da2c49cfe.d15758d7-70f8-4474-9c95-fb984463140a@emailsignatures365.codetwo.com>
2023-11-24 7:04 ` GOOR, Jean-Noel
2023-11-24 12:38 ` Timo Rothenpieler [this message]
[not found] <75bc2482-ee76-46e0-b158-59812d9b556b.6b3277fd-9509-4eec-8a03-dcd135675389.710aff08-3149-4359-b808-f5cd67e63c91@emailsignatures365.codetwo.com>
[not found] ` <75bc2482-ee76-46e0-b158-59812d9b556b.f81fd677-2c20-4d59-96be-51794e3dd064.4d4d527c-2a22-427f-ada8-1e8f5e860956@emailsignatures365.codetwo.com>
[not found] ` <75bc2482-ee76-46e0-b158-59812d9b556b.0878c2f3-5737-4b62-9d31-5d0da2c49cfe.e2ffd514-4b29-4fb8-9897-62d808ad9d0e@emailsignatures365.codetwo.com>
2023-11-23 8:29 ` GOOR, Jean-Noel
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=d8c5103a-509b-414a-a88b-feecb6e06170@rothenpieler.org \
--to=timo@rothenpieler.org \
--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