Closed
Bug 517833
Opened 15 years ago
Closed 14 years ago
Stack exhaustion crash: recursion protection isn't working for DOM Mutation Events
Categories
(Core :: XPConnect, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pvnick, Unassigned)
Details
(Keywords: crash, testcase)
Attachments
(3 files)
Probably not exploitable, but I saw it write to some weird places.
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
bclary: when you get a chance can you run valgrind against this one just to make sure it's simple recursion and not scary
Keywords: qawanted
Summary: Crash [@ XPCConvert::NativeInterface2JSObject] - Stack overflow → Crash [@ XPCConvert::NativeInterface2JSObject] - Stack exhaustion
Comment 3•15 years ago
|
||
Jonas, have you seen this before?
Why isn't our normal recursion-protection helping us here? Seems like another case of doing something in an event handler that causes the event to fire again. Rinse, repeat.
Comment 5•15 years ago
|
||
I didn't see any scary valgrindy stuff on Mac 10.5 for 1.9.{0..3}
Keywords: qawanted
Updated•15 years ago
|
Assignee: general → nobody
Component: JavaScript Engine → XPConnect
QA Contact: general → xpconnect
Updated•14 years ago
|
Comment 6•14 years ago
|
||
I can't reproduce the crash.
You need to log in
before you can comment on or make changes to this bug.
Description
•