Closed
Bug 1228887
Opened 9 years ago
Closed 9 years ago
DOM Notification clone error trips "Assertion failure: !JS_IsExceptionPending(cx)"
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WORKSFORME
| Tracking | Status | |
|---|---|---|
| firefox45 | --- | affected |
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: assertion, testcase, Whiteboard: [fuzzblocker])
Attachments
(2 files)
Assertion failure: !JS_IsExceptionPending(cx), at ./NodeBinding.cpp:117
or
Assertion failure: !cx->isExceptionPending(), at js/src/vm/GlobalObject.cpp:278
|
Reporter | |
Comment 1•9 years ago
|
||
|
|
Reporter | |
Comment 2•9 years ago
|
||
Marking as [fuzzblocker] because these assertions' causes are not shown on the stack.
Whiteboard: [fuzzblocker]
|
||
Comment 3•9 years ago
|
||
I don't seem to get an assertion on a current inbound build. Which build are you using, exactly? Do you see the bug when loading the testcase from Bugzilla, or do you need to run it in some special way?
Flags: needinfo?(jruderman)
|
|
Reporter | |
Comment 4•9 years ago
|
||
Now I get "DataCloneError: The object could not be cloned", so I guess WFM?
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jruderman)
Resolution: --- → WORKSFORME
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•