☂️ 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
Posted by patrickhulce on Nov 9, 2018, 3:30 PM
Tags
Related issues
- [UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
- Server requests and latency increased after upgrading from Next.js 15 to 16
- Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
- Can't download videos from YouTube on cobalt.tools
- `google_service_networking_connection` produce an error when trying to destroy the resource
- WebGPU-based renderer for the editor
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
github (Network)
[UPDATE NOW] PHP RCE Vulnerability (CVE-2026-109618 and CVE-2026-109619)
Server requests and latency increased after upgrading from Next.js 15 to 16
Leak of Geedge Networks internal documents (100,000+ from Jira, Confluence, GitLab)
Can't download videos from YouTube on cobalt.tools
`google_service_networking_connection` produce an error when trying to destroy the resource
WebGPU-based renderer for the editor
Zed downloads NodeJS binary and npm packages from Internet without user’s consent
FR: Allow custom domains for Tailscale Funnel
☂️ 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
Comments (0)
No comments yet. Start the discussion.