From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 2/3] avcodec/cbs_av1: Clear obu.metadata on error Date: Thu, 1 Jun 2023 21:33:14 -0300 Message-ID: <467d8078-3b3a-4e10-a07e-e4f2cd1edd60@gmail.com> (raw) In-Reply-To: <AS8P250MB0744DE198DDE8A6E042396468F4EA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> On 6/1/2023 9:28 PM, Andreas Rheinhardt wrote: > 1. Before 97f4263, the current_obu was reset (and the packet effectively > discarded) upon errors from ff_cbs_read_packet(); yet this is no longer > true and it seems that the contents of current_obu will be processed in > the next call to av1_receive_frame(). This change seems to have been > unintentional. I guess I assumed that ff_cbs_read_packet() failing would clear the CodedBitstreamFragment before returning, but if that's not the case then ff_cbs_fragment_reset() should be called. Would something like > diff --git a/libavcodec/av1dec.c b/libavcodec/av1dec.c > index 5cc5d87c64..d1a0f6eaa2 100644 > --- a/libavcodec/av1dec.c > +++ b/libavcodec/av1dec.c > @@ -1461,6 +1461,7 @@ static int av1_receive_frame(AVCodecContext *avctx, AVFrame *frame) > ret = ff_cbs_read_packet(s->cbc, &s->current_obu, s->pkt); > if (ret < 0) { > av_packet_unref(s->pkt); > + ff_cbs_fragment_reset(&s->current_obu); > av_log(avctx, AV_LOG_ERROR, "Failed to read packet.\n"); > return ret; > } Be enough? _______________________________________________ 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-06-02 0:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-01 22:25 [FFmpeg-devel] [PATCH 1/3] tools/target_dec_fuzzer: adjust threshold for RKA Michael Niedermayer 2023-06-01 22:26 ` [FFmpeg-devel] [PATCH 2/3] avcodec/cbs_av1: Clear obu.metadata on error Michael Niedermayer 2023-06-02 0:28 ` Andreas Rheinhardt 2023-06-02 0:33 ` James Almer [this message] 2023-06-02 20:13 ` Michael Niedermayer 2023-06-02 20:19 ` Michael Niedermayer 2023-06-01 22:26 ` [FFmpeg-devel] [PATCH 3/3] avcodec/mpeg4videodec: more unsigned in amv computation Michael Niedermayer 2023-09-04 19:11 ` [FFmpeg-devel] [PATCH 1/3] tools/target_dec_fuzzer: adjust threshold for RKA Michael Niedermayer
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=467d8078-3b3a-4e10-a07e-e4f2cd1edd60@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