The default bug view has changed. See this FAQ.

"ASSERTION: Must know the source we were loading from"

RESOLVED FIXED in mozilla6

Status

()

Core
Audio/Video
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: Jesse Ruderman, Assigned: cpearce)

Tracking

(Blocks: 1 bug, {assertion, testcase})

Trunk
mozilla6
x86
Mac OS X
assertion, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

(Reporter)

Description

7 years ago
Created attachment 478862 [details]
testcase

This is a variant on bug 593305 that triggers an additional assertion.  (The second assertion is the "new" one.)

###!!! ASSERTION: Load event should not be delayed at start of resource selection.: '!mDelayingLoadEvent', file content/html/content/src/nsHTMLMediaElement.cpp, line 632

###!!! ASSERTION: Must know the source we were loading from!: 'mSourceLoadCandidate', file content/html/content/src/nsHTMLMediaElement.cpp, line 688
(Reporter)

Comment 1

7 years ago
Created attachment 478864 [details]
stack traces
(Assignee)

Comment 2

7 years ago
Thanks for the testcase Jesse!
(Assignee)

Comment 3

7 years ago
The assertion "Must know the source we were loading from!" no longer occurs thanks to the landing of bug 604067. The "Must know the source we were loading from" assertion still occurs.
(Assignee)

Comment 4

7 years ago
(In reply to comment #3)
> The assertion "Must know the source we were loading from!" no longer occurs
> thanks to the landing of bug 604067. The "Must know the source we were loading
> from" assertion still occurs.

Oops, I mean the assertion "Load event should not be delayed at start of resource
selection." still occurs.
(Reporter)

Comment 5

6 years ago
Now I get this assertion instead, which seems like it's kind of the opposite:

###!!! ASSERTION: Load event not delayed during source selection?: 'mDelayingLoadEvent', file content/html/content/src/nsHTMLMediaElement.cpp, line 527
(Assignee)

Comment 6

6 years ago
(In reply to comment #5)
> Now I get this assertion instead, which seems like it's kind of the opposite:
> 
> ###!!! ASSERTION: Load event not delayed during source selection?:
> 'mDelayingLoadEvent', file content/html/content/src/nsHTMLMediaElement.cpp,
> line 527

This occurs because we're receiving an OnStartRequest for a channel which has been cancelled because we've started a new load. We're dispatching an error event in this case to the element (which is where we're triggering the assertion), even though the element has started a new load, and isn't necessarily in an error state. We should not dispatch an error event in the OnStartRequest for a channel which is no longer the currently loading channel; we'll have dispatched "emptied" and "abort" events when the new load aborts/cancels the old load.
(Assignee)

Comment 7

6 years ago
Created attachment 529913 [details] [diff] [review]
Patch v1

* Abort in an nsMediaLoadListener's OnStartRequest() (without firing an error event) if the load has been cancelled.

Patch is greenish on Try
http://tbpl.mozilla.org/?tree=Try&rev=e99e885e06a4
Assignee: nobody → chris
Status: NEW → ASSIGNED
Attachment #529913 - Flags: review?(roc)
Comment on attachment 529913 [details] [diff] [review]
Patch v1

Review of attachment 529913 [details] [diff] [review]:

Can we check in a test based on Jesse's test?
Attachment #529913 - Flags: review?(roc) → review+
(Assignee)

Comment 9

6 years ago
(In reply to comment #8)
> Can we check in a test based on Jesse's test?

No need really. This assertion was randomly failing with my patch for bug 652751 applied in content/media/test/crashtests/459431-1.html, so that effectively is a testcase.
(Assignee)

Comment 10

6 years ago
http://hg.mozilla.org/mozilla-central/rev/eb15fab87e7e
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Target Milestone: --- → mozilla6
(Assignee)

Comment 11

6 years ago
(In reply to comment #9)
> This assertion was randomly failing with my patch for bug 652751 applied 

Oops, I meant with my patch for bug 650994 applied.
You need to log in before you can comment on or make changes to this bug.