Stuck on an issue?
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.
Failing to reliably connect to Chrome on 4.7.0 when using -b chrome --headless
See original GitHub issueWhen upgrading to 4.7.0 (from 4.6.0) we are getting error messages when connecting to chrome about 50-75% of the time, this was not a problem before 4.7.0 (we have used Cypress for a couple of years now).
It only happens when we use -b chrome --headless
Versions
4.7.0 Windows 10 Chrome 83
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:35 (1 by maintainers)
Top Results From Across the Web
Selenium Webdriver tests not running on Chrome headless ...
Selenium Webdriver tests not running on Chrome headless due to "unable to connect to renderer" error · Ask Question. Asked 3 years, 7...
Read more >Chrome (headless) process stuck - Google Groups
The main Chrome process gets stuck at using 10-30% memory but under 5% CPU, yet unresponsive. Several child processes (for the open tabs...
Read more >Launching Browsers | Cypress Documentation
The Chrome browser is evergreen - meaning it will automatically update itself, sometimes causing a breaking change in your automated tests. We host...
Read more >Installing Google Chrome On CentOS, Amazon Linux, or RHEL
We use headless Chrome instances for web scraping on Amazon Linux here at ... all of the unmet dependencies that would normally make...
Read more >Running Selenium Headless Tests on Outlook shows older ...
I also ran the test using chrome headless mode but it didn't attach the screen shot for the failed tests , but edge...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I get this issue commonly on macOS Catalina and the latest Cypress versions. Not sure how to replicate, but the fix is to kill the orphaned Chrome process.
I’m getting this error locally as well. I’m running MacOS BigSur 11.5, Chrome Version 92.0.4515.107, Cypress 7.5.0. It only occurs when I’m not running headless. I can run headless just fine.
Edit: restarting my machine seems to have fixed my issue.