[Bug 22065] New: Loop in 3.5.7 Coded Frame Processing

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22065

            Bug ID: 22065
           Summary: Loop in 3.5.7 Coded Frame Processing
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: jdsmith@microsoft.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

There seems to be an infinite loop in the updated spec in “sequence” mode:

3.5.7 Coded Frame Processing

1.5.3 Set the discontinuity flag to true.
1.8.1 If mode equals “sequence”, set the sequence start timestamp equal to the
highest presentation end timestamp.
1.8.6 Jump to the Loop Top step above to restart processing of the current
coded frame.
1.5.3 Set the discontinuity flag to true.
1.8.1 If mode equals “sequence”, set the sequence start timestamp equal to the
highest presentation end timestamp.
1.8.6 Jump to the Loop Top step above to restart processing of the current
coded frame.
1.5.3 Set the discontinuity flag to true.
1.8.1 If mode equals “sequence”, set the sequence start timestamp equal to the
highest presentation end timestamp.
1.8.6 Jump to the Loop Top step above to restart processing of the current
coded frame.
1.5.3 Set the discontinuity flag to true.
1.8.1 If mode equals “sequence”, set the sequence start timestamp equal to the
highest presentation end timestamp.
1.8.6 Jump to the Loop Top step above to restart processing of the current
coded frame.
…

We believe that the 1.5.3 step is probably just supposed to set the need random
access point flag instead (which means the discontinuity flag is no longer set
and can be eliminated).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 16 May 2013 18:18:03 UTC