From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/v4l2_context: suppress POLLERR when buffers are uninitialized
Date: Thu, 27 Jul 2023 21:18:38 +0200 (CEST)
Message-ID: <1fd88bea-9395-ff36-1b92-bee98327225@passwd.hu> (raw)
In-Reply-To: <20230725213838.199190-2-mailingradian@gmail.com>
On Tue, 25 Jul 2023, Richard Acayan wrote:
> A POLLERR occurs when libavcodec attempts to dequeue output buffers
> before enqueuing capture buffers. This could happen to an application
> deciding to send the first coded packet. Suppress these POLLERRs when
> the buffers are uninitialized.
Will apply, thanks.
Marton
>
> See https://trac.ffmpeg.org/ticket/9957 for the original bug report.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
> Changes since v1 (20230718220017.3336-1-mailingradian@gmail.com):
> - stopped emitting POLLERR logs for this case (thanks to feedback from
> Marton Balint)
>
> libavcodec/v4l2_context.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/v4l2_context.c b/libavcodec/v4l2_context.c
> index a40be94690..f20f713e1d 100644
> --- a/libavcodec/v4l2_context.c
> +++ b/libavcodec/v4l2_context.c
> @@ -325,9 +325,13 @@ start:
>
> /* 0. handle errors */
> if (pfd.revents & POLLERR) {
> - /* if we are trying to get free buffers but none have been queued yet
> - no need to raise a warning */
> + /* if we are trying to get free buffers but none have been queued yet,
> + * or if no buffers have been allocated yet, no need to raise a warning
> + */
> if (timeout == 0) {
> + if (!ctx->buffers)
> + return NULL;
> +
> for (i = 0; i < ctx->num_buffers; i++) {
> if (ctx->buffers[i].status != V4L2BUF_AVAILABLE)
> av_log(logger(ctx), AV_LOG_WARNING, "%s POLLERR\n", ctx->name);
> --
> 2.41.0
>
> _______________________________________________
> 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".
prev parent reply other threads:[~2023-07-27 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 21:38 Richard Acayan
2023-07-27 19:18 ` Marton Balint [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=1fd88bea-9395-ff36-1b92-bee98327225@passwd.hu \
--to=cus@passwd.hu \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=mailingradian@gmail.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