"ASSERTION: didn't call Disconnect" with XMLHttpRequestUpload.onabort

RESOLVED FIXED

Status

()

defect
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: jruderman, Assigned: smaug)

Tracking

(Blocks 1 bug, {assertion, testcase})

Trunk
x86
macOS
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

Reporter

Description

11 years ago
Posted file testcase
Steps to reproduce:
1. Load the testcase.
2. Quit Firefox using Cmd+Q.

Result:

###!!! ASSERTION: didn't call Disconnect: '!mTarget', file /Users/jruderman/central/content/events/src/nsEventListenerManager.cpp, line 353

I think the problem is that mListenerManager is set by nsXHREventTarget, a base class for both nsXMLHttpRequestUpload and nsXMLHttpRequest, but only nsXMLHttpRequest's destructor calls Disconnect.  The least disruptive fix would be to make nsXMLHttpRequestUpload's destructor do the same, but it might make more sense to move it to mListenerManager's destructor if that doesn't cause timing issues.
We want Upload's dtor to do the same thing as XHR's dtor.
Assignee: nobody → Olli.Pettay
Status: NEW → ASSIGNED
Attachment #341101 - Flags: superreview?(jst)
Attachment #341101 - Flags: review?(jst)
Attachment #341101 - Flags: superreview?(jst)
Attachment #341101 - Flags: superreview+
Attachment #341101 - Flags: review?(jst)
Attachment #341101 - Flags: review+
Reporter

Updated

11 years ago
Flags: in-testsuite+
Reporter

Comment 3

11 years ago
I think Smaug forgot to mark this as FIXED.

Fix:
http://hg.mozilla.org/mozilla-central/rev/a19ab7286802

Crashtest:
http://hg.mozilla.org/mozilla-central/rev/bad67e7ea71b
Status: ASSIGNED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.