Media Decode Error spike and fallback - explanation?
Reported by
jamie.st...@redspace.com,
Sep 28
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: Play Widevine Encrypted Media served through DASH. What is the expected behavior? What went wrong? We have been regularly experiencing approximately 1% error rate for users with media decode errors. However, on September 24 and 25, we experienced a spike in users encountering issues during playback. Was Chrome running any user-tests or experiments related to this code path at this time? We haven't changed any configuration or code on our side and are trying to get to the bottom of this increase. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.14.0 Flash Version: We have identified a few other issues with our content, which resulted in https://crbug.com/889311 being filed by Matt Wolenetz. We're in the process of fixing our MP4 metadata to be more accurate as well, but that hasn't hit production yet.
,
Oct 8
Thanks for filing the issue! @Reporter: Could you please share a sample test file/URL which helps us to triage the issue further in a better way. Any further inputs from your end may be helpful.
,
Nov 12
Mac triage: assigning directly to dalecurtis@ - I know this issue is stale though so maybe it's WontFix?
,
Nov 18
Hello, unfortunately I don’t have a file or URL to share due to the service that was experiencing this problem is no longer getting any support. However, from my own investigation and media-internals logs we received from internally reproduced cases this appeared to center around the CHUNK_DEMUXER_ERROR_APPEND_FAILED. With the suberror: “Failed to parse video for decode” (something close to that, iirc). The filed bug from Matt Wolenetz was what the internal team decided to wait on. It got attached to the MSEBufferByPTS flag. At that point, a content re-encode with proper sample flags was decided to be to much risk/cost as the service was falling out from support. If you aren’t seeing the issue on a wide-scale then feel free to mark as wontfix. Otherwise to recreate: package a CMAF segmented MP4 with Widevine encryption, use mp4 trun first_sample_flags to mark first sample as sync. Have multiple GoPs in single track run with sync samples marked as unknown. Expect message in media log about mismatched keyframe analysis from MP4 metadata. Play content in backgrounded tab ( we never personally reproduced in foreground tab ). After ~2 hours of playback in this scenario we anecdotally had a high reproduction rate.
,
Nov 19
|
||||
►
Sign in to add a comment |
||||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 30