Lighthouse: Lighthouse doesn't run in DevTools on Chromium Linux

[stramel]

EDIT: All chromium users with a non-matching git hash don't get the audits2 remote module. Unfortunately a diff bug than the chromeOS one.

---

I'm running a Asus Chromebook C302CA on the Beta Channel.

Chromium 60

When I go to my website and try to run the lighthouse audit on it, it just spins and never does anything other than switch to a mobile view.

[patrickhulce]

@stramel got a URL for us?

[stramel]

It was https://d-demo-ci.salesnext.com/login but it did work using the extension.

[patrickhulce]

Hm yeah seems to be working fine in Canary as well

[stramel]

@patrickhulce it was only with the audit through dev tools on my Chromebook. I didn't get any error messages either. I ended up having to close the tab to kill the audit.

[patrickhulce]

We're unable to reproduce with latest version, please re-comment if you're still experiencing this to re-open!

[stramel]

@patrickhulce I am still able to reproduce this.

Chromium Version 62.0.3202.89 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)
Lighthouse 2.6.0

Works with the Chrome Extension doesn't work with the DevTools.

Can you please re-open?

[patrickhulce]

@stramel I'm able to audit that page in both Chrome Stable and Canary DevTools on both OS X and Ubuntu. Can you provide more information on steps you take and precisely what behavior you observe?

[stramel]

@patrickhulce I don't think my steps are that abnormal...

Steps to Reproduce w/ Extension

1. Open Chromium 62
2. Check Extension settings, Ensure Lighthouse is allowed to run in incognito
3. Open an incognito tab
4. Navigate to https://d-demo-ci.salesnext.com/login
5. Click the lighthouse extension icon
6. Click "Generate Report"
7. Wait for successful finish

Works as Expected

Steps to Reproduce w/ Dev Tools

1. Open Chromium 62
2. Open an incognito tab
3. Navigate to https://d-demo-ci.salesnext.com/login
4. Open Dev Tools
5. Click the "Audits" tab
6. Click "Perform an audit..."
7. Click "Run audit"

Expected: Same results as extension

Actual: The screen drops to emulating Nexus 5X. The modal where "Run audit" was click switches to a loading indicator, with the words loading. It stays in this state indefinitely.

Clicking "cancel" changes the text to "Canceling" but never actually cancels anything.
Clicking the x in the upper-right corner of the dialog closes the dialog. However, click "Perform an audit" again, then try clicking "cancel" and it does nothing.

NOTE: I did change the URL to a more generic version which still has the same issue.

[patrickhulce]

Hm, strange. I cannot reproduce on this new URL either, but the behavior you're describing seems like DevTools has lost its connection to the tab and not actually started Lighthouse at all. "Loading" should almost immediately be replaced by "Loading page & waiting for onload..." in normal operation.

Are you able to successfully audit any page in DevTools?

[stramel]

@patrickhulce I am not able to successfully audit any page using the DevTools.

Tested usatoday.com and github.com

[stramel]

@patrickhulce The issue is directly an issue with using Chromium not Chrome. I downloaded Google Chrome (stable) and ran the audit using DevTools, everything worked as expected.

[patrickhulce]

Ahhhh thanks for identifying @stramel! We'll have to explore this. Could you provide steps for how you're installing/building Chromium?

[stramel]

Mine comes with my OS, Gallium OS, which is specifically built for Chromebooks. It is listed as chromium-browser recommended under galliumos-desktop package.

[devsware]

If this can help, the same issue (as explained and documented by @stramel ) happens running Lighthouse via Chromium 63 Developers Tools on Linux Mint (installed via apt).

On the same PC, Lighthouse on Google Chrome Version 63.0.3239.84 (Official Build) (64-bit) works as expected and completes the audits.

This is the "About Chromium" content:
Version 63.0.3239.84 (Official Build) Built on Ubuntu , running on LinuxMint 18.1 (64-bit)

[hhofstaetter]

The same issue happens on Chromium 63 under Ubuntu installed from official apt repos:

Version 63.0.3239.84 (Official Build) Built on Ubuntu , running on Ubuntu 16.04 (64-bit)

[paulirish]

I'm guessing the remote module download fails due to an unmatched git hash.

see also #4132, which has an upstream bug at https://crbug.com/747349

[nzhuk98]

I can consistently reproduce the same exact issue described in https://github.com/GoogleChrome/lighthouse/issues/2627#issuecomment-345770177 in Debian 9.3 Stretch.

Installed from stretch/updates/main:

Version 64.0.3282.119 (Developer Build) built on Debian 9.3, running on Debian 9.3 (64-bit)

Version 62 from stretch/main doesn't work either:

Version 62.0.3202.89 (Developer Build) built on Debian 9.1, running on Debian 9.3 (64-bit)

[jasomdotnet]

I confirm this issue too:

Version 64.0.3282.119 (Official Build) Built on Ubuntu , running on Ubuntu 14.04 (32-bit)

Lighthouse never finish the loading. Long live to Webpagetest :-)

[N0ps32]

I have the same issue on

Version 64.0.3282.186 (Official Build) (64-bit)

On

Version 65.0.3325.106 (Official Build) beta (64-bit)

Lighthouse does finally start running tests. but after it finishes no report is being generated.

OS: Arch Linux

[Serkan-devel]

Same on
Chromium: 64.0.3282.119 (Entwickler-Build) built on Debian 9.3, running on Debian 9.4 (64-Bit)

[Serkan-devel]

Has the reason why it's happening already been found?

[patrickhulce]

@Serkan-devel Yes remote modules are not supported on all Chrome versions, see root cause crbug for discussion

[Serkan-devel]

the link isn't viewable on my end, even when logged in

[patrickhulce]

Ah, apologies didn't realize it's restricted.

Summary: remote devtools modules (such as audits/a11y/device frames/network "product" labels/etc) are not supported for some Chrome build processes, Chrome OS and Chromium Linux for example. Fix has landed in ToT for Chrome OS.

[Serkan-devel]

How far is it for the fix to to be ported from ChromiumOS to other Linux distros?

[mnalis]

Chromium also hang here after displaying "Lighthouse is warming up..."
on Version 66.0.3359.117 (Developer Build) built on Debian 9.4, running on Debian 9.4 (64-bit)

in console there is error:
[8627:8627:0516/201607.774326:ERROR:CONSOLE(1)] "Uncaught (in promise) SyntaxError: Invalid or unexpected token", source: chrome-devtools://devtools/bundled/audits2_worker.js?remoteBase=https://chrome-devtools-frontend.appspot.com/serve_file/@1634af79e3bf0d6f0178a5fdb8829b059ead4b26/ (1)

[stefanmaric]

For me it also hangs on "Lighthouse is warming up..." using stable build:

Version 66.0.3359.181 (Official Build) Built on Ubuntu , running on Ubuntu 17.10 (64-bit)

[Serkan-devel]

Is there any progress

[patrickhulce]

There has been some progress, yes. Chrome OS is now bundled directly and should work in m69.

Chromium builds are still blocked, but there's a proposed approach that might work in most cases. Likely 1-2 releases out still.

[Serkan-devel]

I think it now works on 67.0.3396.87 (Entwickler-Build) built on Debian 9.4, running on Debian 9.4 (64-Bit)

[devsware]

It's a good news for Debian users, but unfortunately it still freezes on Version 67.0.3396.99 (Official Build) Built on Ubuntu , running on LinuxMint 18.1 (64-bit)

[Serkan-devel]

@devsware your version looks a little newer than mine. And isn't there a significant difference between debian and debian based distros, like ubuntu/mint?

[devsware]

@Serkan-devel I agree that our systems are a bit different, even if Linux Mint is Ubuntu derived and Ubuntu is based on Debian.

Mine was just a quick test to check the status of Lighthouse on my system and I wanted to give a feedback about using it on Ubuntu (or Ubuntu derived) distro as soon as possible.

[N0ps32]

Also works on Arch Linux now!

[jasonworden]

Does Lighthouse's Chrome Launcher support Chromium by default, if Chrome or Chrome Canary are not installed?

Would I need to specify the Chromium path by the CHROME_PATH flag? (looking at https://www.npmjs.com/package/lighthouse)

[patrickhulce]

@jasonworden if it's on your path already and you're on linux, yes!

https://github.com/GoogleChrome/chrome-launcher/blob/6316362c585ad1dfd85562d488d0f2644fcdca15/src/chrome-finder.ts#L111-L117

[brendankenny]

Looks like this is more or less fixed now that the remote module bug is fixed and released.