LibWeb: Stacking context painted twice on newrelic.com & interia.pl

[shannonbooth]

Seen by loading these two pages:

For interia.pl:

319479.700 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.700 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.700 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.710 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.710 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>
319479.740 WebContent(479681): FIXME: Painting commands are recorded twice for stacking context: SVGGeometryBox<path>

[shannonbooth]

The same crash is also happening on https://newrelic.com

[kuchikuu]

Perhaps interia.pl also suffers from the same crash so I'm going to comment here.

https://interia.pl:
7f0bafdbd0c49b3c69bbecbe0ef076918158fe65 - no crash (fixed)
aede0100960b6b9cacd0e5a0bd0887bd34651e29 - crash
b1b7e2324ad52908ab8e49826327c975996c06bf - crash
f5799f7d2cc44d1d8323265d95242fcaaf8604e3 - crash (nytimes.com doesn't crash here)
527ad9ac016c86b7c5b15600da92ecd7731964e7 - crash (nytimes.com doesn't crash here)
.
.
398ae75 - crash
8893836b60d5209a7223161c16f6ae668a2e5d91 - no crash

2024-05-05.18-51-24.mp4

https://nytimes.com
7f0bafdbd0c49b3c69bbecbe0ef076918158fe65 - no crash
130aff12b16f6ab0fb2832b9e6deb5fe5721ea9d - no crash
b1b7e2324ad52908ab8e49826327c975996c06bf - no crash
f5799f7d2cc44d1d8323265d95242fcaaf8604e3 - no crash
527ad9ac016c86b7c5b15600da92ecd7731964e7 - no crash
398ae75f9a35dc9022dc44992d9955178093e07b - no crash
8893836b60d5209a7223161c16f6ae668a2e5d91 - no crash

https://newrelic.com/
7f0bafdbd0c49b3c69bbecbe0ef076918158fe65 - still a crash
f5799f7d2cc44d1d8323265d95242fcaaf8604e3 - crash
527ad9ac016c86b7c5b15600da92ecd7731964e7 - crash
398ae75f9a35dc9022dc44992d9955178093e07b - crash
8893836b60d5209a7223161c16f6ae668a2e5d91 - crash

[nico]

#24226 turned this into a dbgln() probably.

[shannonbooth]

#24226 turned this into a dbgln() probably.

Yup crash for this reason is gone. nytimes.com is still crashing, but looks to be for an unrelated problem which I can't seem to get a backtrace for. I'll adjust this issue to just track the stacking contexts issue, and will raise another issue for the crash in nytimes