Details
Description
Steps to reproduce:
- ./simplebrowser https://css-tricks.com/
Assert with 77-based:
[1:1:0212/134405.286656:FATAL:ng_inline_node.cc(1300)] Check failed: **max_size_out == ComputeContentSize(node, container_writing_mode, input, NGLineBreakerMode::kMaxContent, max_size_cache, nullptr) ("2580.7" vs. "2575.14")0x67db16266d0:LayoutNGBlockFlow P
Assert with 79-based:
[11641:1:0212/134919.931613:FATAL:ng_inline_node.cc(1750)] Check failed: (*max_size_out)->Round() == content_size.Round() (2581 vs. 2575)0x292340e26d10:LayoutNGBlockFlow P
I can only reproduce this on Linux.
Similar issues are reported for Chromium too (eg. https://bugs.chromium.org/p/chromium/issues/detail?id=1006849 ). They are usually closed as WontFix because the negligible difference between values. We should probably just suppress this assert because it is easily reproducible with WebEngine.
Attachments
For Gerrit Dashboard: QTBUG-82060 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
290382,2 | Suppress DCHECK triggered by NGInlineNode::ComputeMinMaxSize | 77-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |
290384,2 | Suppress DCHECK triggered by NGInlineNode::ComputeMinMaxSize | 79-based | qt/qtwebengine-chromium | Status: MERGED | +2 | 0 |