1581653 - ASSERTION: Column set should be complete if the available block-size is unconstrained on 812893.html

Status: NEW

(Core :: Layout: Columns, defect, P5)

Description

[Ting-Yu Lin [:TYLin] (PDT, UTC-7)]

After enabling column-span, running layout/generic/crashtests/812893.html generates assertions like

[Child 410, Main Thread] ###!!! ASSERTION: Column set should be complete if the available block-size is unconstrained: 'aStatus.IsFullyComplete() || aReflowInput.AvailableBSize() != NS_UNCONSTRAINEDSIZE', file /home/aethanyc/Projects/gecko/layout/generic/nsColumnSetFrame.cpp, line 1307
Block(form)(4)@7f2eef73f508: Init: bad caller: height WAS 756222600(0x2d130a88)
Block(form)(4)@7f2eef73f508: Init: bad caller: height WAS 756215640(0x2d12ef58)
Block(form)(4)@7f2eef73f508: Init: bad caller: height WAS 756198540(0x2d12ac8c)
Block(form)(4)@7f2eef73f508: Init: bad caller: height WAS 756190440(0x2d128ce8)
[Child 410, Main Thread] ###!!! ASSERTION: Column set should be complete if the available block-size is unconstrained: 'aStatus.IsFullyComplete() || aReflowInput.AvailableBSize() != NS_UNCONSTRAINEDSIZE', file /home/aethanyc/Projects/gecko/layout/generic/nsColumnSetFrame.cpp, line 1307

Comment 1

[Ting-Yu Lin [:TYLin] (PDT, UTC-7)]

The assertions happen only on this particular crashtest, which contains large numbers in the style. Any reasonable web page shouldn't have them. I don't feel this worth blocking shipping column-span.