Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lingjiang Fang <vacingfang@hotmail.com>
To: Lingjiang Fang <vacingfang@foxmail.com>
Cc: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc: fix h264 parser bug
Date: Mon, 16 May 2022 18:37:33 +0800
Message-ID: <BY5PR18MB3153F0EF854B82F2871ED654D5CF9@BY5PR18MB3153.namprd18.prod.outlook.com> (raw)
In-Reply-To: <tencent_1A5A746EF0F810A9AFC4A3D70231D4069009@qq.com>

On Fri, 13 May 2022 00:22:02 +0800
Lingjiang Fang <vacingfang@foxmail.com> wrote:

ping for review
padding zero after pps may lead to decode crash in same ipads
btw, I am working on update fate cases to fit this bugfix

> will give a wrong nalu length(+1) when next nalu start with 00000001
> this bug will lead to an padding zero to pps in AVC Sequence
> header(flv) or in avc1(mpr)
> 
> ---
> 
>  libavcodec/h2645_parse.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/libavcodec/h2645_parse.c b/libavcodec/h2645_parse.c
> index 03780680c6..2e941a2bd0 100644
> --- a/libavcodec/h2645_parse.c
> +++ b/libavcodec/h2645_parse.c
> @@ -134,6 +134,10 @@ int ff_h2645_extract_rbsp(const uint8_t *src,
> int length, dst[di++] = src[si++];
>  
>  nsc:
> +    if (src[si-1] == 0) {
> +        --di;
> +        --si;
> +    }
>      memset(dst + di, 0, AV_INPUT_BUFFER_PADDING_SIZE);
>  
>      nal->data = dst;



Regards,
Lingjiang Fang
_______________________________________________
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".

      reply	other threads:[~2022-05-16 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 16:22 Lingjiang Fang
2022-05-16 10:37 ` Lingjiang Fang [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=BY5PR18MB3153F0EF854B82F2871ED654D5CF9@BY5PR18MB3153.namprd18.prod.outlook.com \
    --to=vacingfang@hotmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=vacingfang@foxmail.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