Error [SEVERE]: Timed out receiving message from renderer: 20.000 while executing the testsuite through Selenium on Jenkins

by

This error message…

[30.168][SEVERE]: Timed out receiving message from renderer: 20.000

…implies that the ChromeDriver was unable to initiate a new Chrome browser process.

Your main issue is the version compatibility between the binaries you are using as follows :

  • You are using chromedriver=2.33
  • Release Notes of chromedriver=2.33 clearly mentions the following :

Supports Chrome v60-62

  • You are using chrome=64.0
  • Release Notes of ChromeDriver v2.35 clearly mentions the following :

Supports Chrome v62-64 (includes the browser version you are using)

  • Your Selenium Client version is 3.8.1.
  • Your JDK version is 1.8.0_151 which is pretty older.

So there is a clear mismatch between the JDK v8u151 , Selenium Client v3.8.1 , ChromeDriver v2.33 and Chrome Browser v64.0

Solution

  • Upgrade JDK to recent levels JDK 8u162.
  • Upgrade Selenium to current levels Version 3.11.0.
  • Upgrade ChromeDriver to current ChromeDriver v2.38 level.
  • Keep Chrome version at Chrome v66.x levels. (as per ChromeDriver v2.38 release notes)
  • Clean your Project Workspace through your IDE and Rebuild your project with required dependencies only.
  • Use CCleaner tool to wipe off all the OS chores before and after the execution of your Test Suite.
  • If your base Web Client version is too old, then uninstall it through Revo Uninstaller and install a recent GA and released version of Web Client.
  • Take a System Reboot.
  • Execute your @Test.

More Related Contents:

  1. NoSuchElementException, Selenium unable to locate element
  2. How does chrome driver interact with Chrome browser?
  3. Using implicit wait in selenium
  4. Selenium Google Login Block
  5. How to run Selenium WebDriver test cases in Chrome
  6. SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 81
  7. Is there a version of Selenium WebDriver that is not detectable?
  8. Page load strategy for Chrome driver (Updated till Selenium v3.12.0)
  9. Many process of Google Chrome (32 bit)
  10. release Selenium chromedriver.exe from memory
  11. unknown error: Chrome failed to start: exited abnormally (Driver info: chromedriver=2.9
  12. What is benefit of using ChromeDriver over WebDriver if we are using only Chrome Browser in our Selenium Automation Script
  13. How to turn off w3c in chromedriver to address the error unknown command: Cannot call non W3C standard command while in W3C
  14. Selenium Chrome Browser org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start
  15. ERROR:ssl_client_socket_openssl.cc(1158)] handshake failed with ChromeDriver Chrome browser and Selenium
  16. Cannot get automation extension from timeout: Timed out receiving message from renderer
  17. Getting Timed out receiving message from renderer: 600.000 When we execute selenium scripts using Jenkins windows service mode
  18. Selenium how to manage wait for page load?
  19. Selenium use chrome on Colab got unexpectedly exited
  20. selenium.common.exceptions.SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 80
  21. WebDriverError: disconnected: unable to connect to renderer
  22. How to run Selenium tests on the Brave web browser?
  23. Only local connections are allowed Chrome and Selenium webdriver
  24. How to open Chrome browser console through Selenium?
  25. java.lang.IllegalStateException: The path to the driver executable must be set by the webdriver.chrome.driver system property
  26. Timed out receiving message from renderer: 0.100 log messages using ChromeDriver and Chrome v80 through Selenium Java
  27. Unable to hide “Chrome is being controlled by automated software” infobar within Chrome v76
  28. Chrome – org.openqa.selenium.WebDriverException: unknown error: cannot get automation extension at driver.manage().window().maximize();
  29. Undetected Chromedriver not loading correctly
  30. How to solve ‘Getting Default Adapter failed’ error when launching Chrome and try to access a webpage using the ChromeDriver using Selenium

Leave a Comment