Chrome v88 and ChromeDriver v88 causing Timed out receiving message from renderer

[Evangelos R]

After running some regression tests for approx 3hrs, the following error started appearing when trying to get to a url.

This was not an issue prior to upgrading.

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 27.190 (Session info: chrome=88.0.4324.150) Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03' System info: host: 'xxxx', ip: 'xxx', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_261' Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 88.0.4324.150, chrome: {chromedriverVersion: 88.0.4324.96 (68dba2d8a0b14..., userDataDir: , goog:chromeOptions: {debuggerAddress: localhost:xxx}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}

[hasheer a s]

This same issue is happening for our test script as well.. Any workaround for this.. Please advise 

[Jeff White]

Workaround is this:

Set pageload strategy to none. After I did, it fixed that error, though I had to handle waits better because of it. 

--
You received this message because you are subscribed to the Google Groups "ChromeDriver Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/chromedriver-users/0d8dc0d7-5d5d-4e0e-882f-77459c3c5771n%40googlegroups.com.

[Evangelos R]

Setting the page load strategy to none causes other issues.

I'm still experiencing this. I'm now running on an Azure agent, and it's happening quite often.

Has anyone found a workaround?

I can see in the v89 release notes, it's been fixed: (Resolved issue 3667: Timed out receiving a message from renderer)

Is there anyone else who has worked out what the cause is and how this can be fixed?

E

[Yariv Hastilow]

We have also been struggling with this issue since upgrading to Chrome/Driver v88.
We tried the v89 beta last week and the same issue is still present.

We are running 2 instances of the browser within Apache Tomcat in an AWS EC2 instance, and when this issue starts to occur it quickly fills the memory and brings down Tomcat as well.
Comparison of our testing with different instance sizes:

v83 / t3.small EC2 instance (2GB memory): No issues 
v88 / t3.small EC2 instance (2GB memory): Issue occurs after around 2-4 hours

v89 beta / t3.small EC2 instance (2GB memory): Issue occurs after around 2-4 hours

v88 / t3.medium (4GB memory): Issue occurs after around 12-18 hours

v88 / t3.large (8GB memory): No issues so far (running 10+ days)

We can't afford to pay 4 times the server costs to keep running a t3.large server just to avoid this issue, but it seems to work for us in the short term.
We cannot set the page load strategy to NONE for other reasons, so currently we are looking at switching to Firefox as the only long-term solution.

[Evangelos R]

Yariv, I've noticed this occurring a lot more frequently when running an in an Azure Agent.

There must be something we do that is different to others, because it doesn't appear to be affecting everyone.

Are you running tests in parallel? (I'm running 5 threads). Perhaps a thread safety issue?

Who knows...

The last time I saw this issue was last year on an early v88 chrome version, and i believe they fixed the chrome driver for that specific error.

If we can understand what the cause is, or what we're doing differently, then we can fix it or work around the issue.

E

[Yariv Hastilow]

@Evangelos

> Are you running tests in parallel? (I'm running 5 threads). Perhaps a thread safety issue?

Yes, we have 2 threads in parallel.
We also noticed that after the issue occurs, various parts of Chrome/ChromeDriver are sometimes left in memory, so there could be even more than 2...
It could be worth us trying 1 thread per t3.small instance, at least then the total cost would only be 2x instead of 4x!

In case you aren't familiar with AWS EC2, the only difference between the t3.small/medium/large instances is the memory size, so the available memory seems to have a big influence on this issue. Are you able to try your tests with different memory sizes?

[Evangelos R]

I see what you're saying about memory size being a factor... perhaps a memory leak somewhere or we're not cleaning up the chrome driver properly?

this is how I shutdown the browser:

if(getDriver() != null) {
getDriver().quit();
driver.set(null);
}

My research shows that if the browser is not cleared(closed/destroyed/disposed) correctly, if may cause memory leak issues.

I'm going to direct some efforts here report on any findings.

E

[Yariv Hastilow]

@Evangelos

Thanks, we would be very interested to see your results. We have basically decided to try switching to Firefox because we've spent a lot of time on this issue and got nowhere, but I will also post here if I find anything new.

We shut down with:

if (Objects.nonNull(driver)) {

  driver.close();

  driver.quit();

}

but I believe that only one of close/quit is necessary.
We have been running this setup for a couple of years and didn't have any memory issues until upgrading to v88, but it certainly does look like there is a memory leak occurring in conjunction with this issue. On the other hand, we had expected the 8GB memory we now have to get full after a couple of days, but it seems to be OK, so perhaps the leak is only happening when cleaning up AFTER the renderer timeout issue, rather than being the cause of it? Though with 4GB, it extended the time before the issue occurred, so we really don't know...

[Evangelos R]

@Yariv,

The other thing I want to explore which is kind of unique, is the way I check for elements to exist...

getDriver().manage().timeouts().implicitlyWait(0, TimeUnit.SECONDS);

try {
isPresent = getDriver().findElements(by).size() > 0;
}catch (NoSuchWindowException noSuchWindowException){
isPresent = false;
}

getDriver().manage().timeouts().implicitlyWait(30, TimeUnit.SECONDS);

Also, do you set any chrome options, I've been trying all different options without any luck...

[Yariv Hastilow]

@Evangelos

It seems to get stuck during all kinds of operations for us, including RemoteWebDriver.findElementsByXPath and RemoteWebElement.click. 

Here is an example exception for reference:

Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'

System info: host: 'ip-10-9-22-72.ap-northeast-1.compute.internal', ip: '10.9.22.72', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.214-160.339.amzn2.x86_64', java.version: '11.0.10'

Driver info: org.openqa.selenium.chrome.ChromeDriver

Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 88.0.4324.150, chrome: {chromedriverVersion: 88.0.4324.96 (68dba2d8a0b14..., userDataDir: /tmp/.com.google.Chrome.46ctS3}, goog:chromeOptions: {debuggerAddress: localhost:44495}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, proxy: Proxy(), setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}

Session ID: be2fa3c1a17f18685b149607cf8351b2

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 180.000

(Session info: headless chrome=88.0.4324.150)

Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'

System info: host: 'ip-10-9-22-72.ap-northeast-1.compute.internal', ip: '10.9.22.72', os.name: 'Linux', os.arch: 'amd64', os.version: '4.14.214-160.339.amzn2.x86_64', java.version: '11.0.10'

Driver info: org.openqa.selenium.chrome.ChromeDriver

Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 88.0.4324.150, chrome: {chromedriverVersion: 88.0.4324.96 (68dba2d8a0b14..., userDataDir: /tmp/.com.google.Chrome.46ctS3}, goog:chromeOptions: {debuggerAddress: localhost:44495}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: LINUX, platformName: LINUX, proxy: Proxy(), setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}

Session ID: be2fa3c1a17f18685b149607cf8351b2

at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)

at org.openqa.selenium.remote.http.W3CHttpResponseCodec.createException(W3CHttpResponseCodec.java:187)

at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:122)

at org.openqa.selenium.remote.http.W3CHttpResponseCodec.decode(W3CHttpResponseCodec.java:49)

at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158)

at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)

at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552)

at org.openqa.selenium.remote.RemoteWebElement.execute(RemoteWebElement.java:285)

at org.openqa.selenium.remote.RemoteWebElement.click(RemoteWebElement.java:84)

at porters.esi.core.webdriver.ChromeCrawlWebElement.click(ChromeCrawlWebElement.java:26)

at porters.esi.crawler.RanCrawler.doGetLoginList(RanCrawler.java:293)

at porters.esi.crawler.RanCrawler.getLoginList(RanCrawler.java:154)

at porters.esi.servlet.LoginListCrawlerRunnable.crawlLoginList(LoginListCrawlerRunnable.java:126)

at porters.esi.servlet.LoginListCrawlerRunnable.crawl(LoginListCrawlerRunnable.java:74)

at porters.esi.servlet.CrawlerRunnable.run(CrawlerRunnable.java:107)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:829)

Our driver settings/options are:

driver.manage().timeouts().pageLoadTimeout(180, TimeUnit.SECONDS).implicitlyWait(100, TimeUnit.MILLISECONDS).setScriptTimeout(180, TimeUnit.SECONDS);

options.addArguments("--headless");

options.addArguments("--disable-gpu");

options.addArguments("--incognito");

options.addArguments("--disable-extensions");

options.addArguments("--window-size=1920,1080");

options.addArguments("--start-maximized");

options.addArguments("--disable-features=VizDisplayCompositor");

[Evangelos R]

@Yariv.

Can I ask, Are you using Mavens surefire plugin? what's your setup/pom?

I am, and have moved on to seeing in some config changes will help. 

[Yariv Hastilow]

@Evangelos

> Can I ask, Are you using Mavens surefire plugin? what's your setup/pom?

No, we are using Gradle for build.

[Evangelos R]

@Yariv,

I also tried v89 chrome.... still the same problem!!!

[Yariv Hastilow]

@Evangelos
At least neither of us is alone then! Something is clearly still broken. 

Was your system OK on earlier versions of Chrome? We were using v83 before updating to v88, so I don't know if the issue happened in v84~87.

[Evangelos R]

@Yariv,

Looks like google have now gone live with Version 89.0.4389.72 (Official Build) (64-bit).

I'll be looking at this later today.

If you get a chance to test it out, I'd be interested to see your findings.

Evan

[Evangelos R]

@Yariv.

An update for you and anyone else in the forum who may have the same issue...

I've now tried the latest Chrome Version  89.0.4389.72 and latest driver version:  89.0.4389.23.

So, results look promising! A little too early to say 100% though, but looking good so far.

I'd suggest that you also give this a crack and see if it helps with your issues. I'd be very keen to hear if this works for you too.

And if anyone else can share their findings, that would be great!

Evan

[Yariv Hastilow]

We have upgraded to 89.0.4389.72 + 89.0.4389.23, but unfortunately we are still experiencing the same error.

> Session ID: 6980d9a2842484adf33011c4e52e0c48

> org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 180.000

> (Session info: headless chrome=89.0.4389.72)

[Evangelos R]

After further testing. This issue still occurs...

It does not occur my local machine that has heaps of RAM etc... so definitely related to system performance...

Is there anyone that can help further please?

I thought this was fixed in the latest driver.

[kanthis...@gmail.com]

This issue hampers a lot even after upgrading to chrome 89 (browser and driver). Is there any workaround or solution to this. 

Also we tried to suppress the event by setting System.setProperty(ChromeDriverService.CHROME_DRIVER_SILENT_OUTPUT_PROPERTY, "true") but with no luck

TimeoutException: timeout: Timed out receiving message from renderer: 90.000
 (Session info: chrome=89.0.4389.90)
 (Driver info: chromedriver=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}),platform=Windows NT 10.0.17763 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 90.11 seconds
Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'xxxxxxx', ip: 'xxxxx', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_181'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{mobileEmulationEnabled=false, timeouts={implicit=0.0, pageLoad=300000.0, script=30000.0}, hasTouchScreen=false, platform=XP, acceptSslCerts=false, goog:chromeOptions={debuggerAddress=localhost:49709}, acceptInsecureCerts=false, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, setWindowRect=true, webauthn:extension:largeBlob=true, unexpectedAlertBehaviour=ignore, applicationCacheEnabled=false, rotatable=false, networkConnectionEnabled=false, chrome={chromedriverVersion=89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}), userDataDir=C:\Users\Administrator\Provar\TestRobertHalf\.chromeProfiles\profile0}, takesHeapSnapshot=true, pageLoadStrategy=normal, strictFileInteractability=false, databaseEnabled=false, handlesAlerts=true, version=89.0.4389.90, browserConnectionEnabled=false, proxy=Proxy(direct), nativeEvents=true, locationContextEnabled=true, cssSelectorsEnabled=true, webauthn:virtualAuthenticators=true}]
Session ID: xxxxxxxxxxxxxxxxxxxxxxxx]