Closed Bug 1064699 Opened 5 years ago Closed 5 years ago
Last Video Frame Time after it's used for computing the frame duration
The patch in bug 1062101 turns out to be incorrect because it sets mLastVideoFrameTime when it reads the packet tstamp, but as it's not used to compute the frame duration until slightly later, when it's finally used to compute the final frame's duration it ends up calculating a zero duration. This partially explains the difference between the buffered range end time and the last decoded frame end time mentioned in bug 1062055.
Attachment #8486228 - Flags: review?(cajbir.bugzilla) → review+
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in before you can comment on or make changes to this bug.