Chrome 73.0.3686.75 not compatible with Chromedriver v2.46 or v73.0.3683.68

[Randall Myers]

The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...

error="timeout: Timed out receiving message from renderer: 10.00

[John Chen]

Our testing didn't reveal any compatibility issues between Chrome 73.0.3683.75 and ChromeDriver 2.46 or 73.0.3683.68. Please double check that your latest Chrome was installed correctly, and probably trying running your script on a different machine. If you're still having issues, please provide some more details (such as repro code and logs from ChromeDriver), and we can take a look.

On Tue, Mar 12, 2019 at 5:47 PM Randall Myers <rsmy...@gmail.com> wrote:

The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...

error="timeout: Timed out receiving message from renderer: 10.00

--
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.
For more options, visit https://groups.google.com/d/optout.

[mr.hud...@gmail.com]

Seeing Similar issue as well, two separate PC's.
Tests run fine locally or from Maven command, but when running same "mvn test" through jenkins. Test will hang indefinitely after the handshake is made.

Have tried 73.0.3683.75 and ChromeDriver 2.46.
Noticed issue once Chrome updated to 73, worked fine with ChromeDriver72 and below.
Only temp fix i found was to install an Offline Chrome 72, even works while still using the ChromeDriver73. Its just when running on Chrome73 or higher that this occurs.

[Randall Myers]

I have six Win 2012 R2 servers running Selenium python scripts w/ chromedriver.  Two of those six servers had Chrome updated yesterday to the latest stable release and both are exhibiting the same behavior with this rendering error.  I tried uninstalling / re-installing Chrome with no luck, also tried both Chromedriver v2.46 and and v73.0.3683.68, same results.  I did make one observation, I am able to manually run the scripts from cmdln without errors, its only the task scheduler jobs that when they run get this rendering error and chrome just hangs.

Attached are two sets of logs, the failed set are the task scheduler version and the successful are my manual executions so you can compare.

To unsubscribe from this group and stop receiving emails from it, send an email to chromedriver-users+unsub...@googlegroups.com.

[raymond....@gmail.com]

I am also seeing consistent timeouts after updating two Win 2012 R2 Servers to Chrome 73.0.3683.75 and ChromeDriver 73.0.3683.68.

Tests run fine locally.

[jarosla...@leveris.com]

Any solution here?

I have a same problem everytime I try to make a screenshot:
[1552636837.732][SEVERE]: Timed out receiving message from renderer: 10.000
Chrome: 73.0.3683.75 (Official Build) (64-bit)
ChromeDriver 73.0.3683.68
OS: Windows Server 2012 R2

I have a stacktrace:
org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from renderer: 10.000
(Session info: headless chrome=73.0.3683.75)
(Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Windows NT 6.3.9600 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'WIN-XXX', ip: 'XXX', os.name: 'Windows Server 2012 R2', os.arch: 'amd64', os.version: '6.3', java.version: '1.8.0_111'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities {acceptInsecureCerts: true, acceptSslCerts: true, applicationCacheEnabled: false, browserConnectionEnabled: false, browserName: chrome, chrome: {chromedriverVersion: 73.0.3683.68 (47787ec04b6e3..., userDataDir: C:\Windows\TEMP\scoped_dir1...}, cssSelectorsEnabled: true, databaseEnabled: false, goog:chromeOptions: {debuggerAddress: localhost:60422}, handlesAlerts: true, hasTouchScreen: false, javascriptEnabled: true, locationContextEnabled: true, mobileEmulationEnabled: false, nativeEvents: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: XP, platformName: XP, proxy: Proxy(), rotatable: false, setWindowRect: true, strictFileInteractability: false, takesHeapSnapshot: true, takesScreenshot: true, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unexpectedAlertBehaviour: ignore, unhandledPromptBehavior: ignore, version: 73.0.3683.75, webStorageEnabled: true}
Session ID: 76db5204c8be03b0b4ab39b878cec1c5
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_111]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_111]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_111]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_111]
at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:80) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:44) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:158) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:552) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:609) ~[selenium-remote-driver-3.141.59.jar:?]
at org.openqa.selenium.remote.RemoteWebDriver.getScreenshotAs(RemoteWebDriver.java:295) ~[selenium-remote-driver-3.141.59.jar:?]
at com.XXX.core.gui.Driver.takeScreenshot(Driver.java:387) [automation-core-5.0.32.jar:?]
at com.XXX.core.config.ProjectConfig.embedScreenshot(ProjectConfig.java:153) [automation-core-5.0.32.jar:?]
at com.XXX.XXX.XXX.teardown(XXX.java:63) [classes/:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_111]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_111]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_111]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_111]
at cucumber.runtime.Utils$1.call(Utils.java:40) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.Timeout.timeout(Timeout.java:16) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.Utils.invoke(Utils.java:34) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.java.JavaHookDefinition.execute(JavaHookDefinition.java:60) [cucumber-java-1.2.5.jar:?]
at cucumber.runtime.Runtime.runHookIfTagsMatch(Runtime.java:224) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.Runtime.runHooks(Runtime.java:212) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.Runtime.runAfterHooks(Runtime.java:206) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.model.CucumberScenario.run(CucumberScenario.java:46) [cucumber-core-1.2.5.jar:?]
at cucumber.runtime.junit.ExecutionUnitRunner.run(ExecutionUnitRunner.java:102) [cucumber-junit-1.2.5.jar:?]
at org.junit.runners.Suite.runChild(Suite.java:128) [junit-4.12.jar:4.12]
at org.junit.runners.Suite.runChild(Suite.java:27) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
at cucumber.runtime.junit.ExamplesRunner.run(ExamplesRunner.java:59) [cucumber-junit-1.2.5.jar:?]
at org.junit.runners.Suite.runChild(Suite.java:128) [junit-4.12.jar:4.12]
at org.junit.runners.Suite.runChild(Suite.java:27) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
at cucumber.runtime.junit.ScenarioOutlineRunner.run(ScenarioOutlineRunner.java:53) [cucumber-junit-1.2.5.jar:?]
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:63) [cucumber-junit-1.2.5.jar:?]
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:18) [cucumber-junit-1.2.5.jar:?]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:70) [cucumber-junit-1.2.5.jar:?]
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:95) [cucumber-junit-1.2.5.jar:?]
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:38) [cucumber-junit-1.2.5.jar:?]
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) [junit-4.12.jar:4.12]
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) [junit-4.12.jar:4.12]
at cucumber.api.junit.Cucumber.run(Cucumber.java:100) [cucumber-junit-1.2.5.jar:?]
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369) [surefire-junit4-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275) [surefire-junit4-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239) [surefire-junit4-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160) [surefire-junit4-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:373) [surefire-booter-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:334) [surefire-booter-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:119) [surefire-booter-2.20.1.jar:2.20.1]
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:407) [surefire-booter-2.20.1.jar:2.20.1]

[Vitalii Plagov]

We started to experience exactly the same issue with Chrome 73 and chromedriver 73. We're using Selenide (wrapper around Selenium).

Test just hangs for a very long time and eventually fails with a timeout exception. That happens on Jenkins, while locally it works fine.

m�rts 15, 2019 2:44:03 PM com.codeborne.selenide.drivercommands.LazyDriver getAndCheckWebDriver
INFO: No webdriver is bound to current thread: 1 - let's create a new webdriver
Starting ChromeDriver 73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72) on port 27287
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
m�rts 15, 2019 2:44:05 PM org.openqa.selenium.remote.ProtocolHandshake createSession
INFO: Detected dialect: OSS
m�rts 15, 2019 2:44:05 PM com.codeborne.selenide.webdriver.BrowserResizer adjustBrowserSize
INFO: Set browser size to 1920x1080
[1552654446.848][SEVERE]: Timed out receiving message from renderer: 600.000

[527...@gmail.com]

Same issue here

[zal...@gmail.com]

середа, 13 березня 2019 р. 02:47:10 UTC+2 користувач Randall Myers написав:

> The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...
>
>
>
> error="timeout: Timed out receiving message from renderer: 10.00

The same issue appeared on TeamCity from last Chrome update.
Tests are running with Docker image usage.

``
WebDriverException: Message: chrome not reachable (Session info: headless chrome=73.0.3683.75) (Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Linux 4.4.0-1012-aws x86_64)
``

[John Chen]

We have confirmed issues with take screenshot when Chrome 73.0.3686.75 is started by a service (such as Jenkins or Task scheduler) on Windows. Please see https://crbug.com/942023 for more details. We apologize for any inconvenience caused by this.

However, we haven't yet been able to observe similar issue on Linux, so we appreciate any help you can provide to enable us to reproduce the issue on Linux. We don't have access to TeamCity, but we have tested take screenshot using Docker image produced by Selenium (selenium/standalone-chrome:3.141.59-lithium), and didn't find any problems.

Thanks,

John

--
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.

[test...@gmail.com]

same issue on my side

[coldnebr...@gmail.com]

On Wednesday, 13 March 2019 00:47:10 UTC, Randall Myers wrote:
> The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...
>
>
>
> error="timeout: Timed out receiving message from renderer: 10.00

Has anyone got a workaround for this? I'm pretty sure I'm getting the same or similar issue, running from Jenkins after Chrome updated itself to v73. I've tried ChromeDriver v2.46 and v73.0.3683.68 and all I get is a timeout error as soon as I try to maximise or resize the browser window (right at the beginning of a test run):

Starting test execution, please wait...
Starting ChromeDriver 73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72) on port 9426

Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.

Failed AddLightboxImageGalleryWithContentToAPage
Error Message:
Test method Www.IntegrationTests.LightboxGalleryFeature.AddLightboxImageGalleryWithContentToAPage threw exception:
OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:9426/session/a8c0c5887d3bcc052b0f941dca861c76/window/current/size timed out after 60 seconds. ---> System.Net.WebException: The operation has timed out

Have burnt a day on this so far....

Thanks

[John Chen]

I am aware of some issues with running Chrome 73 from Jenkins. I don't know any workarounds. Please following https://crbug.com/942023 for updates.

[mr.hud...@gmail.com]

Dirty workaround for now,

I'm using Chrome72 Offline download and using Chrome Options to point to that Chrome binary location

ChromeOptions options = new ChromeOptions(); options.setBinary("C:\\Users\\%USER%\\AppData\\Local\\Google\\Chrome\\Application\\chrome.exe");

Obviously not ideal, and still using an older chrome version. But at least this allows tests to complete without hanging.

I'm also eagerly waiting for a fix

[Debanjan Bhattacharjee]

Jon,

Does that implies that the main issue is with the currently GAed Chrome 73.x but not with ChromeDriver?

Thanks

Dev

[John Chen]

The root cause is indeed in Chrome 73.x, not in ChromeDriver. We are working with Chrome devs to find a solution.

[queve...@gmail.com]

El martes, 12 de marzo de 2019, 18:47:10 (UTC-6), Randall Myers escribió:
> The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...
>
>
>
> error="timeout: Timed out receiving message from renderer: 10.00

We are getting the same issues using the chromedriver 73 and chrome 73.x.
Please let us know if there is any fix for this.

[jarosla...@leveris.com]

Adding Chrome flag --disable-features=VizDisplayCompositor fixes the issue.

[queve...@gmail.com]

Hi Jaros.

Did you change directly the flag in the browser or did you add the flag as arguments into the code?

I tried to modify the flag directly in the browser in the next url: Chrome://flags and I found the Viz Display Compositor (OOP-D) option with its default value, I've changed the value to disabled.


Regards.

[jarosla...@leveris.com]

I changed it in code like (Java):

ChromeOptions options = new ChromeOptions();

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

[David Murphy]

Would you know what the ruby implementation would be in passing this information into the driver? Here is my example. Please forgive the crudeness of my code. I am not sure how to verify the driver is picking up this new option/arg.

Capybara.register_driver :chrome_no_password do |app|
  # 2: disable, other than 2 means enable it
  preferences = {
      "profile.managed_default_content_settings.images" => 1,
      "profile.managed_default_content_settings.popups" => 1,
      "credentials_enable_service" => false,
      "profile.password_manager_enabled" => false

  }

  caps = Selenium::WebDriver::Remote::Capabilities.chrome(
      'chromeOptions' => {
          'prefs' => preferences,

      }
  )
  # args = [ "--headless", "--remote-debugging-port=9222", "--ignore-certificate-errors", "--verbose", "--log-path=c:/chromedriver.log" ]
  #args = ["--start-maximized"]
  args = ["--disable-features=VizDisplayCompositor"]

  Capybara::Selenium::Driver.new(app, {:browser => :chrome, :desired_capabilities => caps, :args => args})
end

Capybara.javascript_driver = :chrome_no_password
Capybara.configure do |config|
  config.default_max_wait_time = 10 # seconds
  config.default_driver = :chrome_no_password
end

[lwb...@gmail.com]

On Tuesday, March 12, 2019 at 8:47:10 PM UTC-4, Randall Myers wrote:
> The latest release of Chrome (73.0.3686.75) does not work with Chromedriver v2.46 or Chromedriver 73.0.3683.68. When I run my selenium script I get the following error...
>
>
>
> error="timeout: Timed out receiving message from renderer: 10.00

Is there any update on this issue? I am seeing this issue with TeamCity wit=
h Chrome 73.0.3683.103 and both chromedriver 2.46 and chromedriver_73.0.368=
3.68. The driver and browser processes are started but they hang and never =
run the tests.

[John Chen]

We are aware of issues with Chrome 73.0.3686.x when it is started by a service (such as Jenkins or Task scheduler) on Windows. Specifically, ChromeDriver may stop responding while taking screenshot, resizing window, or closing window. Please see https://crbug.com/942023 for more details. This issue will be fixed in Chrome 74. Workarounds can be found at https://crbug.com/942023#c58. We apologize for any inconvenience caused by this.

However, we haven't yet been able to observe similar issue on Linux, so we appreciate any help you can provide to enable us to reproduce the issue on Linux. We don't have access to TeamCity, and would appreciate more detail on what happens when you run ChromeDriver on it.

Thanks,

John

[geis...@gmail.com]

Synopsis:

I can reproduce similar failure on Linux

Chrome 73 with web driver 73 work on my test harness below. Chrome 73 or 74 with web driver 74 fail at startup on same.

My test harness:

Jenkins >> (remote) Ubuntu 18.04 VM >> Selenium API >> Selenium Stand-alone server >> local google-chrome

Details: 

I use Selenium API  with  

• Webdriver connecting to a
• Selenium Stand-alone server running on same VM with option: '-role node' on 
• Ubuntu 18.04 on Virtualbox VM 
• hosted also on a Ubuntu 18.04 install.

Selenium is being called by Robot Framework's Selenium library.

I start Selenium test runs with Jenkins using terminal multiplexer: tmux.  This is the only way I have found to get Jenkins to start remote test runs that will open Chrome in current user in this test harness.

Chrome  74.0.3729.108 or 73.0.3683.86 with Chrome web driver 74.0.3729.6 fail to start with the web driver returning failure.

Chrome  73.0.3683.86 with Chrome web driver 73.0.3683.68 works fine in this environment.