Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
☂️ PROTOCOL_TIMEOUT
See original GitHub issuetl;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 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
Issue Analytics
- State:
- Created 5 years ago
- Reactions:131
- Comments:336 (22 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I also experienced this bug in the programmatic usage with the lighthouse. I request to consider this as important
@Yasuslik thanks for the link, I managed to fix it with
lighthouse --chrome-flags="--disable-dev-shm-usage"🥳