☂️ PROTOCOL_TIMEOUT

## tl;dr - Chrome sometimes stops responding, most commonly when trying to clear the cache, so uncheck "Clear storage" and try again.

**Explanation**
This is the umbrella ☂️ issue for all `PROTOCOL_TIMEOUT` error reports. We're collecting all of them in a single place so that we can easily identify which protocol methods are most problematic to prioritize to Chromium domain owners.

`PROTOCOL_TIMEOUT` refers to the situation when Lighthouse has been waiting for Chrome to respond to a single command for more than 30 seconds. `PROTOCOL` refers to the [Chrome DevTools Protocol](https://github.com/ChromeDevTools/devtools-protocol) connection that Lighthouse uses to talk to Chrome.

**If you experienced a protocol timeout issue, please just comment here with the method name, e.g. `Network.clearBrowserCache`**

More recent update: https://github.com/GoogleChrome/lighthouse/issues/6512#issuecomment-924123935