TraceElements: `impactedNodes` is not iterable

[SamTyurenkov]

FAQ

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

URL

https://play-best-games.com/atomic-heart/

What happened?

Actually, in lighthouse it works:

However I wanted to report pagespeed.web.dev version, which errors on multiple checks

What did you expect?

I expect pagespeed.web.dev to show same results as browsers lighthouse feature or at least show the checks results properly, without error.

What have you tried?

I have really no idea, what should I try on my side to debug lighthouse behavior. Please suggest.

How were you running Lighthouse?

web.dev

Lighthouse Version

i used the version that is used on pagespeed.web.dev

Chrome Version

122.0.6261.129

Node Version

OS

Windows 11

Relevant log output

-

[adamraine]

I can reproduce this but not consistently. Looks like TraceElements is throwing an error saying impactedNodes is not iterable.

What's weird is that we handle the undefined/null case so in theory this isn't possible:

https://github.com/GoogleChrome/lighthouse/blob/1d2a380d3c15e5848381fc1dd625837c5dc28ff6/core/gather/gatherers/trace-elements.js#L130

[adamraine]

Artifacts from failing PSI run impacted-nodes.artifacts.json.gz

[RodrigoTomeES]

We are experimented the same error in our website => https://pagespeed.web.dev/analysis/https-bigcrafters-com/5sactpqqk8?form_factor=mobile