Closed
Bug 698299
Opened 13 years ago
Closed 13 years ago
"Assertion failure: !ret && cx->isExceptionPending()" in SecurityWrapper::nativeCall
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla11
People
(Reporter: jruderman, Assigned: luke)
Details
(Keywords: assertion, testcase)
Attachments
(3 files)
Assertion failure: !ret && cx->isExceptionPending(), at js/src/jswrapper.cpp:866 The code containing the assertion was added in: changeset: 949c2cf4c772 user: Luke Wagner date: Tue Oct 04 10:50:25 2011 -0700 summary: Bug 690825 - Add a SecurityWrapper base between JS transparent wrappers and XPConnect security wrappers (r=mrbkap)
Reporter | ||
Comment 1•13 years ago
|
||
Reporter | ||
Comment 2•13 years ago
|
||
Comment 3•13 years ago
|
||
Luke, can you look into this? Also, guessing sg:critical here, but I'm happy to downgrade this if it's not that severe.
Assignee: general → luke
Updated•13 years ago
|
Whiteboard: [sg:critical]
Assignee | ||
Comment 4•13 years ago
|
||
Ah, the assert is bogus: it asserts that, if we return false, an exception is pending. This is not true if we have arrived without pushing a stack frame (in the testcase: via setTimeout + bound function object) in which case ReportError chooses not to throw but to instead report immediately (leaving no exception pending).
Group: core-security
Whiteboard: [sg:critical]
Assignee | ||
Comment 5•13 years ago
|
||
Oops, my previous description of the assert ("it asserts that, if we return false, an exception is pending") is wrong; I should have said: "it asserts that we return false AND an exception is pending"). Same conclusion though: bogus assert.
Attachment #572477 -
Flags: review?(mrbkap)
Updated•13 years ago
|
Attachment #572477 -
Flags: review?(mrbkap) → review+
Assignee | ||
Comment 6•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/71046de4fb6a
Target Milestone: --- → mozilla11
Comment 7•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/71046de4fb6a
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•