From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 1/1] lavc/qsvdec: fix dead loop of qsv decoding Date: Mon, 16 Oct 2023 08:26:48 +0000 Message-ID: <0cde6966499d382573b1bddf81216617fe6a89a7.camel@intel.com> (raw) In-Reply-To: <tencent_962905EEA22547D3062848F3E4D37CF5DF05@qq.com> On Do, 2023-09-14 at 15:08 +0800, zhilizhao(赵志立) wrote: > > > > On Sep 14, 2023, at 14:11, Xiang, Haihao > > <haihao.xiang-at-intel.com@ffmpeg.org> wrote: > > > > > > > This seems like a bug in libmfx/libvpl. > > > > I agree there should be a bug in libmfx/libvpl, but we have to avoid this > > dead > > loop in FFmpeg. > > Is it possible that a normal case which do take more than 500ms now break out > early and return AVERROR(EBUSY)? Thanks for your question. Yes, it is possible. So we can't use this way to fix the problem. BRs Haihao > > On the other hand, this isn’t the only place where dead loops can happen. > Third party encoder/decoder wrappers, especially those operating system > framework > wrappers (e.g., Android MediaCodec) have the same risks. Something like a > interrupt callback in avcodec can be useful if more cases have been found. > > > > > > > > I encountered this problem in video conference scenario. Receive more over > > > 9 > > > RTP h264 video streams simultaneously. > > > > Could you file a bug to https://github.com/oneapi-src/oneVPL-intel-gpu , > > then > > document this issue in your patch ? > > > > Thanks > > Haihao > > > > > > > > 获取 Outlook for iOS<https://aka.ms/o0ukef> > > > ________________________________ > > > 发件人: Anton Khirnov <anton@khirnov.net> > > > 发送时间: Tuesday, August 29, 2023 3:57:00 PM > > > 收件人: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > > > 抄送: tinghu3 <siriushu@hotmail.com> > > > 主题: Re: [FFmpeg-devel] [PATCH v2 1/1] lavc/qsvdec: fix dead loop of qsv > > > decoding > > > > > > Quoting Ting Hu (2023-08-29 09:49:06) > > > > From: tinghu3 <siriushu@hotmail.com> > > > > > > > > MFXVideoDECODE_DecodeFrameAsync always return MFX_WRN_DEVICE_BUSY in > > > > special > > > > scenario. > > > > > > "special scenario"? What special scenario? Is this documented anywhere? > > > This seems like a bug in libmfx/libvpl. > > > > > > -- > > > 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". > > _______________________________________________ > > 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". > > _______________________________________________ > 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". _______________________________________________ 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-10-16 8:27 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-29 7:57 Anton Khirnov 2023-08-31 1:34 ` sirius hu 2023-09-14 6:11 ` Xiang, Haihao 2023-09-14 7:08 ` "zhilizhao(赵志立)" 2023-10-16 8:26 ` Xiang, Haihao [this message] 2023-09-15 6:36 ` sirius hu -- strict thread matches above, loose matches on Subject: below -- 2023-08-29 7:49 Ting Hu
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=0cde6966499d382573b1bddf81216617fe6a89a7.camel@intel.com \ --to=haihao.xiang-at-intel.com@ffmpeg.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