-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to determine tid for renderer process #14798
Comments
Thanks for investigating! I can't reproduce this issue myself but looking at the Chromium code for this, it's definitely possible for a Maybe we should consider a |
Ooof. When I did #14287 I ran the new stuff against every trace I have on my system. Just one of them failed and I started a branch to fix it.. and.. it's almost definitely this bug. I'll get that up and in. @mattzeunert if you still have that trace.. could you throw it on trace.cafe ? I'm not sure about the conditions for this repro, but they look.. atypical. |
Here's the trace https://trace.cafe/t/Eh89oqZQDX |
I am getting the same issue running Lighthouse tests against I can always repro this.
Audits show this error:
Lighthouse 10.0.0 and Chromium 110.0.5481.77 built on Debian 11.6, running on Debian 11.5 (within Docker). How could I supply more info for you folks to troubleshoot? |
Ah, I see there's a PR with a fix already. |
Thanks Matt and @slhck for the repros! Super helpful! We got this one sorted and its going out in v10.0.2 |
Awesome, thanks for the fix! |
FAQ
URL
https://treo.sh/
What happened?
"FrameCommittedInBrowser" event had a
processPseudoId
instead of aprocessId
So
mainFramePids
only containedundefined
and Lighthouse returned an error: "Unable to determine tid for renderer process"What did you expect?
Not to get an error
What have you tried?
Lighthouse returned an error
How were you running Lighthouse?
node
Lighthouse Version
10.0.1
Chrome Version
Version 112.0.5597.0 (Official Build) canary (x86_64 translated), but happens in others too
Node Version
No response
OS
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: