- From: <bugzilla@jessica.w3.org>
- Date: Fri, 24 Apr 2015 19:47:47 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28557 Bug ID: 28557 Summary: Coded frame removal algorithm may introduce discontinuity at end of current coded frame group Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: Media Source Extensions Assignee: wolenetz@google.com Reporter: wolenetz@google.com QA Contact: public-html-bugzilla@w3.org CC: jdsmith@microsoft.com, mike@w3.org, public-html-media@w3.org If a remove() operation or range removal algorithm execution due to coded frame eviction algorithm removes buffer(s) such that a discontinuity in the current coded frame group is introduced, the coded frame processing algorithm currently is unaware; the track buffers' "last decode timestamp", "last frame duration", "highest end timestamp", "need random access point flag", and the sourcebuffer's segment parser loop's "group start timestamp" and "group end timestamp" are neither consulted nor updated. Lack of discontinuity logic execution in these cases could cause a decode sequence whose coded frames' decode dependencies are incorrect due to disjoint appends prior to and after the remove()'d range incorrectly being assumed to be a coherent coded frame group without any discontinuity or "need for a random access point". -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 24 April 2015 19:47:49 UTC