Open
Bug 512405
Opened 16 years ago
Updated 3 years ago
layout/base/crashtests/265986-1.html triggers NS_UNCONSTRAINEDSIZE assertions
Categories
(Core :: Layout, defect)
Tracking
()
NEW
People
(Reporter: jruderman, Unassigned)
Details
(Keywords: assertion, testcase)
Attachments
(1 file, 1 obsolete file)
|
997 bytes,
patch
|
Details | Diff | Splinter Review |
Split from bug 387080: layout/base/crashtests/265986-1.html triggers these assertions.
###!!! ASSERTION: computed width should always be computed: 'computedSize.width != NS_INTRINSICSIZE', file layout/xul/base/src/nsBoxFrame.cpp, line 708
###!!! ASSERTION: no unconstrained widths should be present anymore: 'NS_UNCONSTRAINEDSIZE != aReflowState.ComputedWidth()', file layout/generic/nsBlockReflowState.cpp, line 114
###!!! ASSERTION: should no longer be using unconstrained widths: 'aWidth != NS_UNCONSTRAINEDSIZE', file layout/generic/nsLineLayout.cpp, line 175
###!!! ASSERTION: shouldn't have unconstrained widths anymore: 'NS_UNCONSTRAINEDSIZE != aReflowState.availableWidth', file layout/generic/nsLineLayout.cpp, line 1099
###!!! ASSERTION: shouldn't have unconstrained widths anymore: 'psd->mRightEdge != NS_UNCONSTRAINEDSIZE', file layout/generic/nsLineLayout.cpp, line 2407
###!!! ASSERTION: shouldn't have unconstrained widths anymore: 'psd->mRightEdge != NS_UNCONSTRAINEDSIZE', file layout/generic/nsLineLayout.cpp, line 779
###!!! ASSERTION: shouldn't use unconstrained widths anymore: '(mFrameType == NS_CSS_FRAME_TYPE_INLINE && !frame->IsFrameOfType(nsIFrame::eReplaced)) || frame->GetType() == nsGkAtoms::textFrame || mComputedWidth != NS_UNCONSTRAINEDSIZE', file layout/generic/nsHTMLReflowState.cpp, line 287
###!!! ASSERTION: shouldn't use unconstrained widths anymore: 'availableWidth != NS_UNCONSTRAINEDSIZE', file layout/generic/nsHTMLReflowState.cpp, line 266
###!!! ASSERTION: unconstrained widths no longer supported: 'aContainingBlockWidth != NS_UNCONSTRAINEDSIZE', file layout/base/nsLayoutUtils.cpp, line 2077
Flags: in-testsuite+
| Reporter | ||
Comment 1•15 years ago
|
||
The manifest has been annotated:
asserts(10) asserts-if(MOZ_WIDGET_TOOLKIT=="windows",8) load 265986-1.html
I'll update the manifest to also point at this bug report.
Comment 2•15 years ago
|
||
(In reply to comment #1)
> The manifest has been annotated:
>
> asserts(10) asserts-if(MOZ_WIDGET_TOOLKIT=="windows",8) load 265986-1.html
>
> I'll update the manifest to also point at this bug report.
FWIW, on Mac OS X 10.6, I consistently get 8 assertions as well. Can we just mark it as asserts(8-10)?
| Reporter | ||
Comment 3•15 years ago
|
||
Sure, you can change it to asserts(8-10).
Comment 4•15 years ago
|
||
Attachment #468453 -
Flags: review?(jruderman)
| Reporter | ||
Updated•15 years ago
|
Attachment #468453 -
Flags: review?(jruderman) → review+
Comment 5•15 years ago
|
||
Attachment #468453 -
Attachment is obsolete: true
Updated•15 years ago
|
Keywords: checkin-needed
Comment 6•15 years ago
|
||
Comment on attachment 468523 [details] [diff] [review]
adjust the assertion count (for check-in)
http://hg.mozilla.org/mozilla-central/rev/a2947419d601
Updated•15 years ago
|
Comment 7•15 years ago
|
||
This is not actually fixed yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: --- → mozilla2.0b5
Updated•15 years ago
|
Status: REOPENED → NEW
Target Milestone: mozilla2.0b5 → ---
Comment 8•13 years ago
|
||
I've been hitting an AddressSanitizer error on Linux, just on the crashtest mentioned here. The other bug is bug 800390, not sure if this is possibly related.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•