GoogleChrome / GoogleChrome/lighthouse

PROTOCOL_TIMEOUT from `redirects-http`

Open
#12,636 6 comments 0 reactions 1 assignee Claimed by @connorjclark View on GitHub
P3
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

consistent repro for me locally with CLI.
Doesn't happen in CDT.
Error in LR (when PWA checked): `Rendering canceled - timeout during idle.`

ref #6512

```
yarn start https://www.delicious.com.au/ --only-audits=redirects-http

...

waitFor:warn Timed out waiting for page load. Checking if page is hung... +54s
waitFor:warn Page appears to be hung, killing JavaScript... +11s
status Disconnecting from browser... +42s
ChromeLauncher Killing Chrome instance 41162 +1ms
Driver:warn clearDataForOrigin timed out +11s
GatherRunner disconnect:error connect ECONNREFUSED 127.0.0.1:50656 +22ms
CLI:warn Warning: Chrome process could not be killed because it already exited. +171ms
Runtime error encountered: Waiting for DevTools protocol response has exceeded the allotted time. (Method: Emulation.setScriptExecutionDisabled)
LHError: PROT (shutup bot) OCOL_TIMEOUT
at Timeout. (/Users/cjamcl/src/lighthouse/lighthouse-core/gather/driver.js:322:21)
at listOnTimeout (internal/timers.js:531:17)
at processTimers (internal/timers.js:475:7)
error Command failed with exit code 1.
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.