Selenium/Chromedriver Timeout



After Chrome released their newest version yesterday (64.0.3282), I am now receiving this error rather sporadically:

Timed out receiving message from renderer: 600.000

I’m running about 2,000 selenium tests and I see this failure at a rate of about 1 in 100. There are no reproducible steps as far as I can tell- the tests that fail are different with each iteration. I updated to the newest Chromedriver (2.35), but that didn’t seem to have any effect. I was previously using Selenium 2.41, but have updated to the newest version (3.8.1) hoping that it might help… it did not. I’m completely at a loss as to why this might be occurring. Has anyone else noticed this? Is it possibly a bug with Chrome’s newest release?


It looks like there was an issue with the newest Chrome release. Without the disable-gpu Chromeoption set, the renderer will occasionally timeout. The workaround until Google fixes this (if they do fix it at all) is to add the --disable-gpu attribute to the ChromeOptions.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.