This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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).
Marking all pre-Last Call bugs
Changes committed https://dvcs.w3.org/hg/html-media/rev/63675668846c