search

GoogleChrome / lighthouse

Automated auditing, performance metrics, and best practices for the web.
https://developer.chrome.com/docs/lighthouse/overview/
Apache License 2.0
28.08k stars 9.33k forks source link

Showing "lighthouse is warming up" forever #9484

Closed torfmaster closed 3 years ago

torfmaster commented 4 years ago

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 commented 4 years ago

What is your operating system @torfmaster?

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

connorjclark commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

ghonchesefidi commented 4 years ago

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

gjunming commented 4 years ago

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

image

Morgan-Marshall commented 4 years ago

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

jj-wd commented 4 years ago

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

nurrony commented 4 years ago

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

falldowngoboone commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

stuck on "lighthouse is warming up"

jj-wd commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

datanotion commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

jd1378 commented 4 years ago

Having this issue on Chrome Version 78.0.3904.108 (Official Build) (64-bit) on Windows 10 Home (Build 18362 or May 2019 Update) Edit: (It got fixed by itself, Don't know what changed)

johnweland commented 4 years ago

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

I see. well it seems to be doing the same thing on Windows 1909 as well. On Brave and Chrome, I don't have chromium on this system.

Bert0324 commented 4 years ago

Do have the same problem in

vkaracic commented 4 years ago

I have the same issue on Ubuntu 18.04. on Brave browser: Version 78.0.3904.108 (Official Build) (64-bit)

Tried with the Chrome browser (which is the same version as above) and it worked. Guess Brave is no longer supported (properly). Should we move the conversation over to the brave browser repo? There is already one report https://github.com/brave/brave-browser/issues/7220

journeymanavi commented 4 years ago

I had the same problem today: Chrome: Version 78.0.3904.108 (Official Build) (64-bit) MacOS: 10.14.5 (18F132)

After struggling for some time I installed lighthouse npm package and ran it from the command line and it worked! And, oddly, after that it also started working from within DevTools.

Just though of sharing in case this works for other too.

bsclifton commented 4 years ago

Hi folks - Brave developer here 😄

For Brave, this is a known issue that was captured with https://github.com/brave/brave-browser/issues/3199. We had disabled remote debugging because it was making outbound calls

I recently resolved this in Brave by adding a new Enable Remote Debugging toggle in brave://settings/privacy. Once you turn this on, it'll work again 😄The fix is only in version 1.2 and greater (current stable version is 1.1.23; 1.2 is expected to hit Stable on Jan 6).

Fix is here for those curious: https://github.com/brave/brave-core/pull/4044

realsama commented 4 years ago

same problem here

exterkamp commented 4 years ago

from #10103: OS/windows 7 & Chrome Version/79.0.3945.79

connorjclark commented 4 years ago

Has anyone gotten this from running the latest Canary (81.x) or Dev (80.x) channels? This may have been resolved.

mfkvfn commented 4 years ago

Same problem here. Windows 10 64 bit. Chrome version: 80.0.3970.5 Country: China

Has anyone gotten this from running the latest Canary (81.x) or Dev (80.x) channels? This may have been resolved.

kazpr98 commented 4 years ago

Same problem here on the newest update.

Chrome Version 81.0.4016.0 (Official Build) canary (64-bit).

OS: Mojave 10.14.6

Lespinel82 commented 4 years ago

Same problem with:

Chrome Version 79.0.3945.117 (Official Build) (64-bit) OS: Windows 10

sa2kasov commented 4 years ago

I've updated my Chrome on Windows 10 from 79.0.3945.117 to the latest 79.0.3945.130 and the problem is still appears

genehack commented 4 years ago

I am also seeing this on Win10 and Catalina with 79.0.3945.130.

FWIW, I was able to use the Node CLI to successfully run a report (see https://github.com/GoogleChrome/lighthouse#using-the-node-cli for instructions), so that may be a workaround for folks that are stuck.

ssayanm commented 4 years ago

Hi folks - Brave developer here

For Brave, this is a known issue that was captured with brave/brave-browser#3199. We had disabled remote debugging because it was making outbound calls

I recently resolved this in Brave by adding a new Enable Remote Debugging toggle in brave://settings/privacy. Once you turn this on, it'll work again The fix is only in version 1.2 and greater (current stable version is 1.1.23; 1.2 is expected to hit Stable on Jan 6).

Fix is here for those curious: brave/brave-core#4044

Thank you !! Worked for me on debain 10 with brave

holysoles commented 4 years ago

Happening for me as well on:

Chrome Version 79.0.3945.130 (Official Build) (64-bit) Windows Version: 10.0.18362 N/A Build 18362

davinderpalrehal commented 4 years ago

Happening to me as well, funnily its working fine in Edge

Chrome version: Version 81.0.4033.2 (Official Build) dev (64-bit) Mac OS: Mojave Version 10.14.6

Problem occurs both in incognito mode and normal mode

Same issue in Opera and Brave.

ghost commented 4 years ago

For me as well.

Google Chrome: Version 79.0.3945.130 (Official Build) (64-bit) OS: Manjaro 18.1.5 Juhraya

midzer commented 4 years ago

Jup, can confirm @davinderpalrehal

Chrome Version 81.0.4033.2 (Official Build) dev (64-bit) on Debian

davinderpalrehal commented 4 years ago

@midzer not yet, updated to Chrome Version 81.0.4040.5 (Official Build) dev (64-bit) on Mac OS: Mojave v 10.14.6

Lighthouse is only working with Edge but not working on Chrome, Brave and Opera

keyi6 commented 4 years ago

Mine got stuck at 'lighthouse is warming up' as well.

Version 80.0.3987.87 (Official Build) (64-bit) OS: macOS Catalina Version 10.15.2

KissBalazs commented 4 years ago

Same issue, on an older machine.

Version: 80.0.3987.87 32 bit OS: Windows 7

xPaw commented 4 years ago

This broke for me on 79, and is still broken on 80.0.3987.87.

OS: Windows 10 OS Version 1909

keyi6 commented 4 years ago

Mine got stuck at 'lighthouse is warming up' as well.

Version 80.0.3987.87 (Official Build) (64-bit) OS: macOS Catalina Version 10.15.2

I changed a network and then it worked.

Tschoepel commented 4 years ago

Chromium Version 80.0.3987.87 (Official Build) Arch Linux (64-bit) OS: Manjaro 18.1.5 Also not working...

xPaw commented 4 years ago

I have adblock running on my local network, and chrome-devtools-frontend.appspot.com is blocked in AdAway list, whitelisting that has fixed lighthouse for me.

Lighthouse ought to have a proper error message when it's unable to fetch from there.

ghost commented 4 years ago

I have adblock running on my local network, and chrome-devtools-frontend.appspot.com is blocked in AdAway list, whitelisting that has fixed lighthouse for me.

Lighthouse ought to have a proper error message when it's unable to fetch from there.

That fixed it for me.