From: wangyaqiang <1035567130@qq.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2] lavc/hevc_ps: fix process failed when SPS before VPS in hvcC Date: Fri, 14 Oct 2022 18:13:14 +0800 Message-ID: <tencent_D6CF6E682F3944C5E9B1E709DE08CEF58A05@qq.com> (raw) In-Reply-To: <20220926202125.GW6583@pb2> > 2022年9月27日 04:21,Michael Niedermayer <michael@niedermayer.cc> 写道: > > On Mon, Sep 26, 2022 at 05:38:14PM +0800, 1035567130@qq.com wrote: >> From: Wang Yaqiang <wangyaqiang03@kuaishou.com> >> >> In some videos, SPS will be stored before VPS in hvcC box, >> parse SPS does not depend on VPS, so the video is expected to be processed normally. >> Added "parsed_vps" parameter to indicate whether VPS have been parsed. >> Only VPS have been parsed can be verified during SPS parsing. >> >> Signed-off-by: Wang Yaqiang <wangyaqiang03@kuaishou.com> >> --- >> libavcodec/hevc_ps.c | 3 +-- >> 1 file changed, 1 insertion(+), 2 deletions(-) > > This causes segfaults > > ==816== Invalid read of size 8 > ==816== at 0xFAF178: hevc_parse (in ffmpeg_g) > ==816== by 0xA7A2A6: av_parser_parse2 (in ffmpeg_g) > ==816== by 0x5FC388: parse_packet (in ffmpeg_g) > ==816== by 0x5FDC5D: read_frame_internal (in ffmpeg_g) > ==816== by 0x5FFA10: avformat_find_stream_info (in ffmpeg_g) > ==816== by 0x2F6054: open_input_file (in ffmpeg_g) > ==816== by 0x2FC6AB: ffmpeg_parse_options (in ffmpeg_g) > ==816== by 0x2E8A34: main (in ffmpeg_g) > ==816== Address 0x8 is not stack'd, malloc'd or (recently) free'd > > > [...] Excuse me, we have run tests on our own business and have not found this problem, but it is a hidden risk,really hope you can tell me how to reproduce this problem. Thanks > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > When the tyrant has disposed of foreign enemies by conquest or treaty, and > there is nothing more to fear from them, then he is always stirring up > some war or other, in order that the people may require a leader. -- Plato > _______________________________________________ > 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:[~2022-10-14 10:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-09 13:09 [FFmpeg-devel] [PATCH] " 1035567130 2022-09-09 13:55 ` James Almer 2022-09-09 14:34 ` wangyaqiang 2022-09-26 9:38 ` [FFmpeg-devel] [PATCH v2] " 1035567130 2022-09-26 20:21 ` Michael Niedermayer 2022-09-27 12:20 ` wangyaqiang 2022-10-14 10:13 ` wangyaqiang [this message] 2022-10-14 23:00 ` Michael Niedermayer 2022-10-25 14:29 ` wangyaqiang 2022-10-26 2:23 ` [FFmpeg-devel] [PATCH v3] " 1035567130 2022-11-11 2:25 ` wangyaqiang
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=tencent_D6CF6E682F3944C5E9B1E709DE08CEF58A05@qq.com \ --to=1035567130@qq.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