New issue
Advanced search Search tips

Issue 898393 link

Starred by 4 users
Status: WontFix
Owner:
paulir...@chromium.org
Closed: Oct 25
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Lighthouse NO_TRACING_STARTED errors when using --single-process arg

Reported by pe...@foxandgeese.com, Oct 24 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36

Steps to reproduce the problem:
We are running headless Chrome on AWS Lambda. We run Lighthouse 3.2.1 from Chrome + Puppeteer 1.9.0 orchestration.

What is the expected behavior?
We expect Chrome to produce legitimate Lighthouse reports.

What went wrong?
Lighthouse tests fails, for every URL, with error: "Something went wrong with recording the trace over your page load. Please run Lighthouse again. (NO_TRACING_STARTED)"

We believe the cause is that threadNameEvt gets undefined because CrRenderMain Event is not included in traceEvents. https://github.com/GoogleChrome/lighthouse/blob/b878616eaf60e61dcb614d3c8ee69d08440745fd/lighthouse-core/lib/traces/tracing-processor.js#L213

traceEvents is derived from Tracing.end method of Chromium. https://chromedevtools.github.io/devtools-protocol/tot/Tracing#method-end

If we don't pass "--single-process" args, Lighthouse runs fine on the latest Chromium so we think it may be bug about --single-process and events.

Did this work before? N/A 

Chrome version: 71.0.3563.0  Channel: n/a
OS Version: 
Flash Version:
46888877-a05f4280-ce16-11e8-8f8d-61a823455d0f.png
204 KB View Download

Comment 1 by krajshree@chromium.org, Oct 24

Labels: Needs-Triage-M71 Triaged-ET TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it seems to be related to run Lighthouse 3.2.1 from Chrome + Puppeteer 1.9.0 orchestration.
Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

Comment 2 by jarhar@chromium.org, Oct 25

Owner: paulir...@chromium.org

Comment 3 by paulir...@chromium.org, Oct 25 

Thanks very much for reporting. I'll look into it!

Comment 4 by pfeldman@google.com, Oct 25

Status: WontFix (was: Unconfirmed)
--single-process is not a supported Chrome configuration.

Comment 5 by paulir...@chromium.org, Oct 25 

^ Yes, Indeed. 

We also don't support single-process in puppeteer. I understand your motivation for trying it on Lambda, but Chromium engineers can't help you out.

Comment 6 by pe...@foxandgeese.com, Oct 25 

That's too bad. Using headless Chrome as recently as 69.0.3494.0 with single-process allowed us to successfully run Lighthouse. Only in latter releases has this now stopped working. For others deep-diving this issue, see somewhat related https://github.com/adieuadieu/serverless-chrome/issues/15

Comment 7 by pe...@foxandgeese.com, Oct 26 

> --single-process is not a supported Chrome configuration.

Does this mean --single-process is going away? This will prevent headless Chrome from running on Lambda at all (let alone w/ Lighthouse).
►

Sign in to add a comment