LH:ChromeLauncher Waiting for browser

[MuYi086]

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).
• [X] Yes, my issue is not answered by other FAQs.

URL

https://www.baidu.com

What happened?

System: Win11 x64 After npm i -g lighthouse, I have tried on cmd , git bash and wsl ubuntu bash when I use lighthouse https://www.baidu.com the terminal show LH:ChromeLauncher Waiting for browser. +0ms LH:ChromeLauncher Waiting for browser... +0ms LH:ChromeLauncher Waiting for browser..... +505ms LH:ChromeLauncher Waiting for browser....... +501ms LH:ChromeLauncher Waiting for browser......... +502ms LH:ChromeLauncher Waiting for browser........... +501ms LH:ChromeLauncher Waiting for browser............. +501ms LH:ChromeLauncher Waiting for browser............... +501ms LH:ChromeLauncher Waiting for browser................. +502ms LH:ChromeLauncher Waiting for browser................... +501ms LH:ChromeLauncher Waiting for browser..................... +501ms LH:ChromeLauncher Waiting for browser....................... +501ms LH:ChromeLauncher Waiting for browser......................... +502ms LH:ChromeLauncher Waiting for browser........................... +501ms LH:ChromeLauncher Waiting for browser............................. +501ms LH:ChromeLauncher Waiting for browser............................... +502ms LH:ChromeLauncher Waiting for browser................................. +501ms LH:ChromeLauncher Waiting for browser................................... +502ms LH:ChromeLauncher Waiting for browser..................................... +501ms

What did you expect?

run correct and show me the report

What have you tried?

No response

How were you running Lighthouse?

node

Lighthouse Version

12.0.0

Chrome Version

124.0.6367.92

Node Version

20.12.2

OS

Win11

Relevant log output

LH:ChromeLauncher Waiting for browser. +0ms
  LH:ChromeLauncher Waiting for browser... +0ms
  LH:ChromeLauncher Waiting for browser..... +505ms
  LH:ChromeLauncher Waiting for browser....... +501ms
  LH:ChromeLauncher Waiting for browser......... +502ms
  LH:ChromeLauncher Waiting for browser........... +501ms
  LH:ChromeLauncher Waiting for browser............. +501ms
  LH:ChromeLauncher Waiting for browser............... +501ms
  LH:ChromeLauncher Waiting for browser................. +502ms
  LH:ChromeLauncher Waiting for browser................... +501ms
  LH:ChromeLauncher Waiting for browser..................... +501ms
  LH:ChromeLauncher Waiting for browser....................... +501ms
  LH:ChromeLauncher Waiting for browser......................... +502ms
  LH:ChromeLauncher Waiting for browser........................... +501ms
  LH:ChromeLauncher Waiting for browser............................. +501ms
  LH:ChromeLauncher Waiting for browser............................... +502ms
  LH:ChromeLauncher Waiting for browser................................. +501ms
  LH:ChromeLauncher Waiting for browser................................... +502ms
  LH:ChromeLauncher Waiting for browser..................................... +501ms

[adamraine]

This is not reproducible for me, it likely has something to do with your environment try setting CHROME_PATH to a different version of chrome or using Puppeteer to launch Chrome and use the Node API: https://github.com/GoogleChrome/lighthouse/blob/main/docs/puppeteer.md