How to Get Rid of Severe Timed Out Error in Jenkins
Being bothered by the Severe Timed Out Error in Jenkins? You have come to the right place. The How to Get Rid of Severe Timed Out Error in Jenkins tutorial will teach you how to take care of this vexing issue in a single go.
The error you must be encountering might look something like this:
[1552986403.321][SEVERE]: Timed out receiving message from renderer: 600.000
[1552986523.339][SEVERE]: Timed out receiving message from renderer: 120.000
It means that a certain graphics on your browser which was being fetched was not rendered properly and that it was unable to proceed with the execution and hence the time out. Owing to that timeout it wouldn’t even go to No Element Exception, forget about taking screenshots.
This could be owing to one of the following reasons:
- Memory allocation issues (Check if there are too many driver instances opened in your Task Manager)
- GPU issues
A Solution for memory related issue: If you are on a server you can restart the box you are in so that it closes all the driver instances or you could do that job manually by closing all those processes using the End Task functionality.
How to Get Rid of Severe Timed Out Error in Jenkins
With a simple inclusion of an argument that disables GPU from your chrome, you can take care of this issue. Here’s how to do that:
If you are working with Google Chrome, you might have already used the ChromeOptions class in your code. If not this is the way you define it:
ChromeOptions options = new ChromeOptions();
Getting an error for ChromeOptions class? You need to import the following:
import org.openqa.selenium.chrome.ChromeOptions;
Once you have defined and declared an instance of ChromeOptions you are supposed to make use of that instance to call a method called addArguments() where you can pass a parameter as shown:
options.addArguments("--disable-gpu");
The above code will take care of the Severe Timed Out error you have been getting.
Then of course, it goes without saying, you have to initialize the new object later on like this:
driver = new ChromeDriver(options);
where the instance options needs to punched in as a parameter. Hope you are aware of what a ChromeDriver is.
That’s it!
Now if you will run your code on Jenkins, you will no longer get the Severe Timed Out Receiving Message from Renderer error.
Did it work for you? Tell us about it in the comments section below.
Check out more cool tutorials on Jenkins on our site.
