Issue metadata
Sign in to add a comment
|
VpxVideoDecoder fails to reinitialize after Suspend
Reported by
kosty...@yandex-team.ru,
Nov 23 2016
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 YaBrowser/16.11.0.1822 (beta) Yowser/2.5 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Open vp8 video with a little amount of keyframes which is decoded using VpxVideoDecoder, for example https://yadi.sk/d/oNhtTdYPzHVxP 2. Pause video 3. Wait for 15 seconds until it suspends playback 4. Start playing video What is the expected behavior? Video starts playing immediatly What went wrong? Video fails to play. I've attached log from chrome://media-internals. As you can see, VpxVideoDecoder failed to reinitialize. Actually the source of problem is in libvpx: [7148:5500:1123/150853:ERROR:vpx_video_decoder.cc(536)] vpx_codec_decode() error: Bitstream not supported by this decoder https://chromium.googlesource.com/webm/libvpx/+/master/vp8/vp8_dx_iface.c#297 During resume pipeline creates a new one VpxVideoDecoder and it waits for keyframe. So if you resume playback in the middle of the file, ctx->decoder_init is false and you can easily get P-frame, and it leads to initialization failure. Did this work before? Yes Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? Yes Chrome version: 54.0.2840.99 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 23.0 r0
,
Nov 23 2016
This file does not have correct keyframe metadata, and seeking is indeed broken. It may be surprising that seeking result in corruption while suspend/resume results in decode failure, but a decode error is a reasonable result for either. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by dalecur...@chromium.org
, Nov 23 2016Status: Assigned (was: Unconfirmed)