Closed Bug 1230698 Opened 9 years ago Closed 9 years ago

"Assertion failure: !Failed(), at ErrorResult.h:103" - NS_CreateJSTimeoutHandler

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla45
Tracking Status
firefox45 --- fixed

People

(Reporter: jruderman, Assigned: bzbarsky)

References

Details

(Keywords: assertion, testcase)

Attachments

(3 files)

Attached file testcase (deleted) —
Assertion failure: !Failed(), at ErrorResult.h:103 This assertion was added recently: changeset: https://hg.mozilla.org/mozilla-central/rev/ecb3051bba08 user: Boris Zbarsky date: Fri Nov 20 16:29:41 2015 -0500 summary: Bug 1224007 part 6. Change MaybeSetPendingException to set the ErrorResult state to "not failed", just like SuppressException and StealNSResult already do, and assert in the destructor that the ErrorResult is not Failed().
Attached file stack (deleted) —
Code has been buggy since it landed in bug 918345. The string overload takes an aError argument, but puts a new ErrorResult on the stack and uses that instead.
Blocks: 918345
Flags: needinfo?(peterv)
This is a top crasher in bughunter. In the past week, we've hit this on 167 urls.
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Flags: needinfo?(peterv)
Attachment #8697391 - Flags: review?(peterv) → review+
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: