Closed
Bug 1064699
Opened 10 years ago
Closed 10 years ago
Update mLastVideoFrameTime after it's used for computing the frame duration
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
RESOLVED
FIXED
mozilla35
People
(Reporter: kinetik, Assigned: kinetik)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
1.46 KB,
patch
|
cajbir
:
review+
|
Details | Diff | Splinter Review |
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.
|
Assignee | |
Comment 1•10 years ago
|
||
Attachment #8486228 -
Flags: review?(cajbir.bugzilla)
|
||
Updated•10 years ago
|
Attachment #8486228 -
Flags: review?(cajbir.bugzilla) → review+
|
|
Assignee | |
Comment 2•10 years ago
|
||
|
||
Comment 3•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in
before you can comment on or make changes to this bug.
Description
•