Filed from GoogleChrome/lighthouse-ci#381 (comment)

Provide the steps to reproduce

1. Lots of complicated infrastructure setup described in Feature: Specific exit codes depending on failure lighthouse-ci#381 (comment) :(

AWS Lightsail Node-js server(v12.6.1) at 4 GB RAM, 2 vCPUs, 80 GB SSD.
The folllowing exact commands were run:
1 mkdir node-apps
2 cd node-apps
3 touch apps.js
4 edit apps.js to initiate a server on port 3000
const http = require('http') ;
const server = http.createServer((req,res) => {
res.end("Server Running!") ;
})cd
server.listen(3000) ;
5 npm init - complete the wizard
6 sudo npm install -g lighthouse
6 sudo npm install -g chromium-launcher
7 sudo apt install chromium-browser
8 chromium-browser --product-version
9 sudo npm install -g tcp-port-used
the following lighthouse cli was run
lighthouse https://www.etihad.com/ --chrome-flags="--headless" --output json --output ht
ml --output-path ./myfile.json --collect.settings.disableStorageReset --verbose

What is the current behavior? Chrome appears to crash and then Lighthouse exits with the dreaded protocol took too long error.

What is the expected behavior? Lighthouse returns results.

Environment Information

• Affected Channels: CLI
• Lighthouse version: v6.1.1
• Chrome version: ?
• Node.js version: ?
• Operating System: ?

Related issues
ref #6512

I have been unable to reproduce this error so far, but Chrome crashing in the middle probably should result in a more specific error message with Chrome log output rather than the dreaded protocol message.