Closed
Bug 307280
Opened 19 years ago
Closed 19 years ago
StirDOM/csszen crash [@ nsBlockFrame::Destroy]
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [sg:fix])
Crash Data
Attachments
(2 files)
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20050906
Firefox/1.6a1
Testcase crashes while status bar counter says "1400".
Filing as security-sensitive because the unsimplified testcase uses code from
bug 306663.
Reporter | ||
Comment 1•19 years ago
|
||
Reporter | ||
Comment 2•19 years ago
|
||
Reporter | ||
Comment 3•19 years ago
|
||
I've seen non-zero "random addresses" at the top of the stack, so I think this
crash is exploitable.
Flags: blocking1.8b5?
Whiteboard: [sg:fix]
Reporter | ||
Comment 4•19 years ago
|
||
This is also one of the more common StirDOM crashes, so it makes it harder to
test for other crashes.
Comment 5•19 years ago
|
||
Probably depends on bug 278472
Updated•19 years ago
|
Flags: blocking1.8b5? → blocking1.8b5+
Reporter | ||
Comment 6•19 years ago
|
||
WFM Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1)
Gecko/20050922 Firefox/1.6a1
Trunk Sept 20 - crash
Trunk Step 22 - no crash
Gecko1.8 Sept 22 - no crash
Might have been fixed by the patch in bug 307277, which went in during that
window and fixed another Stir DOM crash found on CSS Zen Garden.
I'll file a new bug if I encounter other crashes with the same signature.
bz, should this bug no longer depend on bug 278472?
Please leave this bug as security-sensitive until a fixed Firefox release has
gone out (most likely Firefox 1.5) *and* bug 306663 has been made public.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Comment 7•19 years ago
|
||
No idea on the dependency; I set it based on the stacks you posted...
Updated•19 years ago
|
Flags: blocking1.8b5+
Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ nsBlockFrame::Destroy]
Reporter | ||
Updated•9 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•