Closed Bug 457776 Opened 16 years ago Closed 16 years ago

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

Categories

(Core :: XML, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Assigned: smaug)

Details

(Keywords: assertion, testcase)

Attachments

(2 files)

Attached 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.
Attached patch proposed patchSplinter Review
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+
Flags: in-testsuite+
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
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: