Closed
Bug 554376
Opened 14 years ago
Closed 14 years ago
Crash [@ nsIFrame::SetNextSibling] on print preview with table stuff
Categories
(Core :: Layout: Tables, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: bernd_mozilla)
References
Details
(Keywords: crash, regression, testcase)
Crash Data
Attachments
(1 file)
224 bytes,
application/xhtml+xml
|
Details |
See testcase, which crashes current trunk build on print preview. It doesn't seem to crash in Firefox3.6. http://crash-stats.mozilla.com/report/index/4d98c7e6-060f-429d-928a-c1a412100323 0 xul.dll nsIFrame::SetNextSibling layout/generic/nsIFrame.h:907 1 xul.dll nsFrameList::RemoveFrame layout/generic/nsFrameList.cpp:133 2 xul.dll nsTableFrame::PushChildren layout/tables/nsTableFrame.cpp:1947 3 xul.dll nsTableFrame::ReflowChildren 4 xul.dll nsTableFrame::ReflowTable layout/tables/nsTableFrame.cpp:1889 5 xul.dll nsTableFrame::Reflow layout/tables/nsTableFrame.cpp:1793 6 xul.dll nsContainerFrame::ReflowChild layout/generic/nsContainerFrame.cpp:756 7 xul.dll nsTableOuterFrame::Reflow layout/tables/nsTableOuterFrame.cpp:1152 8 @0x8957e7f
Reporter | ||
Comment 2•14 years ago
|
||
Broad regression range: it regressed between 2009-09-30 and 2009-10-10. I'll have to download the other builds to get a 1 day regression range.
Comment 3•14 years ago
|
||
The first bad revision is: changeset: 33388:c52390466bd1 user: Boris Zbarsky <bzbarsky@mit.edu> date: Fri Oct 02 12:27:37 2009 -0400 summary: Bug 512336. Make frame lists doubly-linked. r=roc,fantasai
Blocks: 512336
Comment 4•14 years ago
|
||
Reminds me of that other table printing crash we were discussing recently...
Comment 5•14 years ago
|
||
Bug 553972?
Comment 6•14 years ago
|
||
That's the one I was thinking of, yes.
Yeah I suck at getting thing into the tree. This is wfm with my debug build.
fixed by Bug 553972
Assignee: nobody → bernd_mozilla
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Crash Signature: [@ nsIFrame::SetNextSibling]
You need to log in
before you can comment on or make changes to this bug.
Description
•