From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavc/gifdec: unify get_buffer() calls I/P frames Date: Tue, 11 Jul 2023 14:17:14 -0300 Message-ID: <c546aea5-2bf5-0008-3899-e1171b4c7cea@gmail.com> (raw) In-Reply-To: <20230711171223.11878-1-anton@khirnov.net> On 7/11/2023 2:12 PM, Anton Khirnov wrote: > Always call ff_reget_buffer(), which ensures that get_buffer2() is > called with AV_GET_BUFFER_FLAG_REF. > > Fixes #10460. > --- > libavcodec/gifdec.c | 29 +++++++++++------------------ > 1 file changed, 11 insertions(+), 18 deletions(-) > > diff --git a/libavcodec/gifdec.c b/libavcodec/gifdec.c > index f2ab783ef0..af65baabd5 100644 > --- a/libavcodec/gifdec.c > +++ b/libavcodec/gifdec.c > @@ -489,29 +489,22 @@ static int gif_decode_frame(AVCodecContext *avctx, AVFrame *rframe, > return ret; > > av_frame_unref(s->frame); > - if ((ret = ff_get_buffer(avctx, s->frame, 0)) < 0) > - return ret; > - > av_fast_malloc(&s->idx_line, &s->idx_line_size, s->screen_width); > if (!s->idx_line) > return AVERROR(ENOMEM); > - > - s->frame->pict_type = AV_PICTURE_TYPE_I; > - s->frame->flags |= AV_FRAME_FLAG_KEY; > - s->keyframe_ok = 1; > - } else { > - if (!s->keyframe_ok) { > - av_log(avctx, AV_LOG_ERROR, "cannot decode frame without keyframe\n"); > - return AVERROR_INVALIDDATA; > - } > - > - if ((ret = ff_reget_buffer(avctx, s->frame, 0)) < 0) > - return ret; > - > - s->frame->pict_type = AV_PICTURE_TYPE_P; > - s->frame->flags &= ~AV_FRAME_FLAG_KEY; > + } else if (!s->keyframe_ok) { > + av_log(avctx, AV_LOG_ERROR, "cannot decode frame without keyframe\n"); > + return AVERROR_INVALIDDATA; > } > > + ret = ff_reget_buffer(avctx, s->frame, 0); > + if (ret < 0) > + return ret; > + > + s->frame->pict_type = s->keyframe ? AV_PICTURE_TYPE_I : AV_PICTURE_TYPE_P; > + s->frame->flags = AV_FRAME_FLAG_KEY * s->keyframe; There's code setting these two in rframe below the gif_parse_next_image() call, so maybe change it to this instead, and remove the duplication. > + s->keyframe_ok |= !!s->keyframe; > + > ret = gif_parse_next_image(s, s->frame); > if (ret < 0) > return ret; _______________________________________________ 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-07-11 17:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-11 17:12 Anton Khirnov 2023-07-11 17:17 ` James Almer [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=c546aea5-2bf5-0008-3899-e1171b4c7cea@gmail.com \ --to=jamrial@gmail.com \ --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