Showing "lighthouse is warming up" forever

[torfmaster]

Maintainer's Note:

tl;dr - This happens when Chromium fails to fetch the Lighthouse code from the web. Check your network connectivity, ensure there are no proxies that would prevent you from downloading code from a Google server, and try again.

On Brave, you'll have to enable the Remote Debugging option under brave://settings/privacy (thx @bsclifton!)

---

Original Issue:

When running lighthouse on Chromium "75.0.3770.90" to audit www.google.com it is showing the message "lightouse is warming up" forever. Since 2019-07-30. It used to worked in the very exact setup before.
Probably, infrastructure to run lighthouse is unavailable.

[patrickhulce]

What is your operating system @torfmaster?

Also try updating your Chrome version as 75.0.3770.90 is running behind latest stable.

[connorjclark]

This happens when the DT uploader fails. I'm not sure how to check if Lighthouse for a specific version of Chromium uploaded successfully. But it seems the latest versions are good. Please update Chrome and let us know if it is still broken.

[patrickhulce]

IIRC @connorjclark I believe this also happens in certain distributions of Chromium in unusual linux environments, sorta like the #7246 failure but when they disabled remote modules.

[torfmaster]

The operating system is ubuntu 18.04. @patrickhulce I doubt this is caused by my setup as it used to work and stopped working out of the sudden (without having installed any updated of chromium or lighthouse).

[patrickhulce]

In this case yes it is almost definitely the Chrome version. I'm just saying that in general, this issue also has potential interaction with the OS-specific distribution of Chromium.

Did updating to latest stable fix the issue for you @torfmaster?

[aladdin-add]

same issue!

browser: brave 0.68.132 Chromium: 76.0.3809.132
os: macos 10.14.5 (18F132)

please let me know if some more info is needed.

[brendankenny]

Closing as there hasn't been movement in some time. Please comment and we can reopen if you're still seeing this issue.

[ghonchesefidi]

Hi
I still have this problem:
Version 77.0.3865.90 (Official Build) (64-bit)
Linux Ubuntu 18.04.03

[gjunming]

@brendankenny , I have the same problem on macOS Mojave (version 10.14.6) with Chrome Version 77.0.3865.120 (Official Build) (64-bit)

[Morgan-Marshall]

Just seeing this issue after updating to Chrome Version 78.0.3904.70 , Windows 10

[jj-wd]

Have that same issue. Started using Canary for Lighthouse Audits now as a "workaround".

[nurrony]

I am also facing same issue .
Version 0.70.121 Chromium: 78.0.3904.70 (Official Build) (64-bit)
MacOS: 10.15.1

[falldowngoboone]

I am having this issue as well. Additionally, I cannot get anything to show up in the Accessibility pane in either Chrome or Chrome Canary.

MacOS 10.14.6
Chrome 78.0.3904.87

[connorjclark]

Thanks for reporting! I have a theory, but could use your help to verify. I presume you have just updated / downloaded the newest Stable Chrome? Could you try (a few times) completely killing Chrome, restarting, and running Lighthouse via DevTools?

[jj-wd]

I wanted to reproduce the issue before trying to kill the process but it was working again immediately. I've meanwhile rebooted and cleared the cache a dozen times though.

[gab4mad]

In my case it was very simple, but you have to come to this solution...

I had this issue on Windows10 pro with the actual chrome version.
Just startd chrom as admin an the whole thing worked....

I have an issue when working with debian, I guess admin right are needed too, but htis is not verified, but I will try this tomorrow....

[antwake]

Doesn't work for me as well
Mojave 10.14.6 / Chromium: 78.0.3904.97

stuck on "lighthouse is warming up"

[jj-wd]

Meanwhile the error reappered on my end. I could test the restarting / killing theory and it didn't start working even after a couple of times with and without clearing the cache.
I can confirm that it works as admin. I don't have another user to test with to check whether it's just admin or the user context overall.
Canary still works, even with the same sites.

[Mr-Zer0]

I am also experiencing the same issue. The lighthouse never stops warming up.
It happens on both windows 10 and Mac OS Catalina
Both chrome and brave versions are 78.0.3904.108 (Official Build).

[condensed-io]

same for me using brave browser: Version 1.0.0 Chromium: 78.0.3904.97 (Official Build) (64-bit)

[datanotion]

Just adding to the version pool:

Fails with:

Brave - Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit)
Catalina 10.15.1 (19B88)

Works with:

Chrome - Version 78.0.3904.108 (Official Build) (64-bit)
Catalina 10.15.1 (19B88)

[johnweland]

Brave - Version 1.0.1 Chromium: 78.0.3904.108 (Official Build) (64-bit) - fails
Chrome - Version 78.0.3904.108 (Official Build) (64-bit) - works

OS - Pop!_OS 19.10

Chromium Version 78.0.3904.97 (Developer Build) built on Debian buster/sid, running on Debian buster/sid (64-bit) - fails as well but with this error

Protocol error (Tracing.start): 'Tracing.start' wasn't found

Channel: DevTools
Initial URL: http://127.0.0.1:5500/index.html
Chrome Version: 78.0.3904.97
Stack Trace: Error: Protocol error (Tracing.start): 'Tracing.start' wasn't found
    at Function.fromProtocolMessage (devtools://devtools/remote/serve_file/@021b9028c246d820be17a10e5b393ee90f41375e/audits_worker/audits_worker_module.js:1603:121)
    at eval (devtools://devtools/remote/serve_file/@021b9028c246d820be17a10e5b393ee90f41375e/audits_worker/audits_worker_module.js:1209:253)

[patrickhulce]

@johnweland, Debian's build of Chromium intentionally removes Lighthouse + tracing support see #7246

[lmdcao]

CloudReady / Chromium OS, with Chromium browser. Same issue.

[simonwep]

Same issue here with the dev version....

• Google Chrome: 87.0.4259.3 (Official Build) dev (64-bit) (cohort: Dev)
• Revision: dfeb7bdcaf32bc8e7efc0b690677db80d6fc556f-refs/branch-heads/4259@{#6}
• OS: Windows 10 OS Version 2004 (Build 19041.450)
• JavaScript: V8 8.7.75

...chrome stable...

• Google Chrome: 85.0.4183.83 (Official Build) (64-bit) (cohort: Stable)
• Revision: 94abc2237ae0c9a4cb5f035431c8adfb94324633-refs/branch-heads/4183@{#1658}
• OS: Windows 10 OS Version 2004 (Build 19041.450)
• JavaScript: V8 8.5.210.20

...and canary:

• Google Chrome: 87.0.4261.0 (Official Build) canary (64-bit) (cohort: Clang-64)
• Revision: f6a2086636367db737a5aaf4e52c110b3d71dc4b-refs/branch-heads/4261@{#1}
• OS: Windows 10 OS Version 2004 (Build 19041.450)
• JavaScript: V8 8.7.76

[connorjclark]

@simonwep are you using any proxies like PiHole?

[simonwep]

@connorjclark Oh man, yeah I should have checked that - when disabling it it works. The error I get when I run it and PiHole is active is the following:

(Sorry the only time it crashed I made a screenshot, now it's working as the script is now probably cached).
Why would pihole be an issue in this case? Aaaah you even mentioned it earlier in the chat god dammit, I'm so sorry 😅

[connorjclark]

No worries, thanks for verifying!

cc @adamraine looks like we do get an explicit error when a proxy blocks it. Not sure how to catch this from the Lighthouse status panel, though.

[Lofesa]

Same here.
With Chrome Versión 87.0.4264.0 (Build oficial) canary (64 bits) it is warming for ever
With Chrome Versión 85.0.4183.102 (Build oficial) (64 bits) it works.
With Edge Versión 85.0.564.51 (Compilación oficial) (64 bits) it works.
No firewall involved as far as I have tried disabling it.
No matter if Chrome Canary is reinstalled.

[simonwep]

The domain which gets blocked is chrome-devtools-frontend.appspot.com which is apparently part of this blocklist:

It works if you add chrome-devtools-frontend.appspot.com (exact domain is enough) to your whitelist.

[Lovor01]

It does not work for me with Chrome developer Version 87.0.4263.3 (Official Build) dev (64-bit).
no proxies, no add-blockers

[patrickhulce]

Lighthouse is currently broken in Canary (and Dev channel), but the DevTools team is working on a fix.

[adamraine]

Lighthouse is no longer a remote module in m87:
https://chromiumdash.appspot.com/commit/419c91eff66647a4a6a16c3b5f558535c5568791

[Alaa84kh]

Disable these two options from chrome settings:

• Continue running background apps when Google Chrome is closed
• Use hardware acceleration when available

Relaunch chrome then try again

That works for me

[Mavrick2020]

Disable these two options from chrome settings:

• Continue running background apps when Google Chrome is closed
• Use hardware acceleration when available

Relaunch chrome then try again

That works for me

I did changes in the settings as mentioned. However, it didn't help. Still facing the same issue.

[lmdcao]

If it can help you, I could make it work with the Chrome extension https://chrome.google.com/webstore/detail/lighthouse/blipmdconlkpinefehnmjammfjpmpbjk

[patrickhulce]

As #9484 (comment) states, Lighthouse shouldn't show this message moving forward in Chrome once m87 hits stable (~early December 2020). In the meantime, you can use Chrome Canary if this is a limitation for your environment.

[omidazm94]

Disable these two options from chrome settings:

• Continue running background apps when Google Chrome is closed
• Use hardware acceleration when available

Relaunch chrome then try again

That works for me

that worked for me. thanks ((:

[ibds1]

We faced the same issue. We once ran the lighthouse for www.google.com, to check its functionality, and then we lighthoused our sites. It audited the site and generated the report.

If you still face the same issue, start interacting with the site while lighthouse audits, this solves the issue.
Hope this was useful.

Thanks,
iBrain Developers.

[ivanaugustobd]

It's basically completely random for me, closing the tab and trying again until the process really start in 2 second frame window is my go on for now

[AdamZaczek]

I'm having this issue now, after updating chrome.

[xinthose]

It worked for me when I used an incognito tab on my website.

[adamraine]

For anyone encountering this recently, we have an issue open for it #13154

[hanh090]

I solve this problem by kill Chrome and restart again

[matthew-dean]

Getting this issue after not having it before on Chrome Version 112.0.5615.137 (Official Build) (arm64)

[adamraine]

Hey folks I opened a new issue for this happening in Chrome 112 #15026

I'm going to lock this thread because it is very old, if this pops up again please file a new issue.