Open Bug 616255 Opened 14 years ago Updated 2 years ago

"ASSERTION: If it's incomplete and has no nif yet, it must flag a nif reflow" printing page with table root

Categories

(Core :: Printing: Output, defect)

x86_64
Linux
defect

Tracking

()

People

(Reporter: jruderman, Unassigned)

References

Details

(Keywords: assertion, testcase)

Attachments

(2 files, 1 obsolete file)

Attached file testcase (print-to-file to see assertion) (obsolete) (deleted) —
###!!! ASSERTION: If it's incomplete and has no nif yet, it must flag a nif reflow.: 'nextFrame || aStatus & NS_FRAME_REFLOW_NEXTINFLOW', file layout/generic/nsCanvasFrame.cpp, line 503
Attachment #494790 - Attachment is obsolete: true
Attached file stack (deleted) —
Is this a regression or a modified fuzzer? The assert itself is from 2008.
Modified fuzzer, I think. I only started to test printing (to pdf/ps) a few weeks ago.
Still asserts on trunk. ASSERTION: data loss - incomplete row needed more height than available, on top of page: 'rowMetrics.Height() <= rowReflowState.AvailableHeight()', file /builds/slave/m-cen-l64-d-000000000000000000/build/src/layout/tables/nsTableRowGroupFrame.cpp, line 1153 ASSERTION: If it's incomplete and has no nif yet, it must flag a nif reflow.: 'nextFrame || aStatus & NS_FRAME_REFLOW_NEXTINFLOW', file /builds/slave/m-cen-l64-d-000000000000000000/build/src/layout/generic/nsCanvasFrame.cpp, line 695
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: