Closed Bug 697643 Opened 13 years ago Closed 13 years ago

Crash [@ JS_IsExceptionPending] modifying a live NodeList

Categories

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

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla10
Tracking Status
firefox10 - ---

People

(Reporter: jruderman, Assigned: peterv)

References

Details

(Keywords: crash, regression, testcase)

Crash Data

Attachments

(3 files)

No description provided.
Attached file stack trace (debug) (deleted) —
HTMLOptionsCollectionWrapper::setItemAt has: return NS_SUCCEEDED(rv) ? true : Throw(nsnull, rv); but Throw() does XPCThrower::Throw(rv, cx); which does JS_IsExceptionPending(cx) which dereferences cx. Peter, can we just pass in a JSContext to setItemAt? The only caller seems to have a JSContext.
That's what generates the code in question, yes.
Attached patch v1 (deleted) — Splinter Review
Assignee: nobody → peterv
Status: NEW → ASSIGNED
Comment on attachment 570078 [details] [diff] [review] v1 Ideally we'd throw when unwrapping, for that we should probably sprinkle more builtinclass around. But we need to deal correctly with errors from setItemAt anyway.
Attachment #570078 - Flags: review?(bzbarsky)
Attachment #570078 - Flags: review?(bzbarsky) → review+
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
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: