Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`content-visibility:hidden;` halts SEO and Accessibility audits - pegs CPU by generating 200k+ console notices

See original GitHub issue

FAQ

Yes, my issue is not about variability or throttling.
Yes, my issue is not about a specific accessibility audit (file with axe-core instead).

URL

N/A

What happened?

Please forgive me I have no spare time to create a public repro - my assumption is that certain SEO/accessibility tests are attempting to do something within content-visibility:hidden; subtrees.

pegged

What did you expect?

Only a single warning at most, not hundreds of thousands bogging the computer - which are then wiped after Lighthouse finishes its work anyway…

What have you tried?

This bug occurs when running via Chome DevTools, audits complete without issue via CLI. pointer-events:none; didn’t seem to make a difference either ¯_(ツ)_/¯

How were you running Lighthouse?

Chrome DevTools

Lighthouse Version

9.2.0

Chrome Version

Version 99.0.4780.0 (Official Build) canary (64-bit)

Node Version

16.13.0

OS

Windows

Relevant log output

Rendering was performed in a subtree hidden by content-visibility:hidden.

Issue Analytics

State:
Created 2 years ago
Comments:12 (2 by maintainers)

Top GitHub Comments

1reaction

connorjclarkcommented, Jun 27, 2022

1000 still seems like a lot to me. However, Adam’s test case above that does ~1400 resulted in LH still able to finish, so in that sense 1000 is great.

1reaction

josepharharcommented, Jun 27, 2022

I filed a bug to limit the number of console messages: https://bugs.chromium.org/p/chromium/issues/detail?id=1340037 Does 1,000 console messages max sound like a good number?