Closed
Bug 846320
Opened 12 years ago
Closed 12 years ago
Offset mBasePosition by mStartTime when seeking.
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: padenot, Assigned: padenot)
Details
Attachments
(2 files)
1.96 KB,
patch
|
kinetik
:
review+
|
Details | Diff | Splinter Review |
912 bytes,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
I found this when trying to remove all the assertions that fire when doing a content/media mochitest run, I forgot to offset |mSeekTime| by |mStartTime| when assigning to |mBasePosition|, resulting in an assert blowing up repeatedly on test_seek.html, specifically when playing split.webm, that happens to start at 2.00 seconds.
With this, I have 0 assertions firing during a full content/media mochitest run (locally).
Assignee | ||
Comment 1•12 years ago
|
||
Attachment #719477 -
Flags: review?(kinetik)
Assignee | ||
Comment 2•12 years ago
|
||
This patch should be applied on top of the patches from bug 845676.
Attachment #719481 -
Flags: review?(dbaron)
Attachment #719481 -
Flags: review?(dbaron) → review+
Also, there are a lot of assertions in content/media that are firing only on Windows builds... sometimes in *very* large numbers. Does this fix those?
Assignee | ||
Comment 4•12 years ago
|
||
I'll have a look today, I usually don't work on Windows.
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/08a66b173b28
https://hg.mozilla.org/mozilla-central/rev/450783152a46
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Updated•12 years ago
|
Attachment #719477 -
Flags: review?(kinetik) → review+
(In reply to David Baron [:dbaron] (don't cc:, use needinfo? instead) from comment #3)
> Also, there are a lot of assertions in content/media that are firing only on
> Windows builds... sometimes in *very* large numbers. Does this fix those?
For the record, I think these are covered by bug 839650.
You need to log in
before you can comment on or make changes to this bug.
Description
•