From: James Zern via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: James Zern <jzern@google.com> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libvpxdec: Remove redundant unreferencing of AVFrame Date: Mon, 18 Sep 2023 10:17:39 -0700 Message-ID: <CABWgkXLUhxHb3j_TndbbYobo81SLwis5tb=w3xJGnuvfCzw6oA@mail.gmail.com> (raw) In-Reply-To: <AS8P250MB0744E1F14C68BC88947A9E128FFBA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On Mon, Sep 18, 2023 at 5:40 AM Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote: > > The AVFrame of a decoder with the ordinary decode callback > is generically unreferenced on error. > > Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> > --- > libavcodec/libvpxdec.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > lgtm. > diff --git a/libavcodec/libvpxdec.c b/libavcodec/libvpxdec.c > index 72ef5fa9a7..c6187fd5a1 100644 > --- a/libavcodec/libvpxdec.c > +++ b/libavcodec/libvpxdec.c > @@ -317,10 +317,8 @@ static int vpx_decode(AVCodecContext *avctx, AVFrame *picture, > return AVERROR(ENOMEM); > if (ctx->has_alpha_channel) { > picture->buf[1] = av_buffer_ref(img_alpha->fb_priv); > - if (!picture->buf[1]) { > - av_frame_unref(picture); > + if (!picture->buf[1]) > return AVERROR(ENOMEM); > - } > } > for (int i = 0; i < 4; i++) { > picture->data[i] = planes[i]; > -- > 2.34.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".
prev parent reply other threads:[~2023-09-18 17:18 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-18 12:41 Andreas Rheinhardt 2023-09-18 17:17 ` James Zern via ffmpeg-devel [this message]
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='CABWgkXLUhxHb3j_TndbbYobo81SLwis5tb=w3xJGnuvfCzw6oA@mail.gmail.com' \ --to=ffmpeg-devel@ffmpeg.org \ --cc=jzern@google.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