Post#130.How to handle 'Time out receiving message from the renderer' in chrome driver?

How to handle 'Time out receiving message from the renderer' in chrome driver?

Problem Statement: While executing selenium test cases you may encountered with below repetitive error message .

[1587832910.221][SEVERE]: Timed out receiving message from renderer: 0.100

1) Although this message will not harm/ fail your test cases, but it will unnecessarily increase your logs.

2) This error message will keep printing in your console till the driver will find the WebElement . So the number of error message is directly proportional to your WebDriver waiting time.

3) While executing your test cases in any devops pipeline (like Azure active directory), this will print as an error in your test execution report (Let's say in Extent Report). However it will not affect your final pass/fail count.

Note: This issue has been logged as a bug for Selenium but has not yet been fixed (Till today). You will get this issue especially in chrome driver version 80 and 81. (Till date I have experienced with these 2 versions of chrome)

Solution Statement: 

1) As this is a known-issue, it's not actually a failure but a retry attempt to listen to chrome. The severity tag confuses the user, and there is a fix on the way. You can also down grade to version 79 or below to free from this error.

2) If you want to remove this error in chrome version 80/81, then you have to add below line of code in your automation script where you are initializing your chrome driver.

System.setProperty("webdriver.chrome.silentOutput", "true");

Code snippet

System.setProperty("webdriver.chrome.silentOutput", "true");

System.setProperty("webdriver.chrome.driver","E: \\browserDrivers\\chromedriver.exe");

WebDriver driver= new ChromeDriver();

driver.navigate().to("URL");

..Hope this helps to solve your purpose!!