selenium: [🐛 Bug]: Chrome 110: Cannot start session

What happened?

Chrome Version: Version 110.0.5481.177 (Official Build) (x86_64) Chrome Driver Version: 110.0.5481.77

After updating to Chrome 110 and downloading the relevant support driver I can no longer start a session

I cannot find any relevant information on the error specifics

How can we reproduce the issue?

Try launch a session using chrome 110 and chromedriver 110

Relevant log output

`Starting ChromeDriver 110.0.5481.77 (65ed616c6e8ee3fe0ad64fe83796c020644d42af-refs/branch-heads/5481@{#839}) on port 6304
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
[1677671505.261][WARNING]: Browser-wide DevTools client failed to connect: disconnected: unable to connect to renderer
org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: disconnected: not connected to DevTools
  (failed to check if window was closed: disconnected: not connected to DevTools)
  (Session info: chrome=110.0.5481.177) 
Host info: host: 'Adam.local', ip: 'fe80:0:0:0:6c:2c11:1a77:e83c%en0'
Build info: version: '4.6.0', revision: '79f1c02ae20'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '13.2.1', java.version: '17.0.6'
Driver info: org.openqa.selenium.chrome.ChromeDriver`

Operating System

Mac

Selenium version

Java 4.6.0

What are the browser(s) and version(s) where you see this issue?

110.0.5481.177

What are the browser driver(s) and version(s) where you see this issue?

110.0.5481.177

Are you using Selenium Grid?

About this issue

Original URL
State: closed
Created a year ago
Comments: 29 (9 by maintainers)

Most upvoted comments

I think we have a number of different things being discussed in this thread as if they were the same thing.

Some of this might be permissions issues, some of this might be mismatch of driver issue, and it’s possible there might be a chromedriver bug involved as well.

It’s hard to know what’s going on without more information. I recommended turning on logging and taking a look at the relevant input/output before the exception: https://www.selenium.dev/documentation/webdriver/troubleshooting/logging/

If it appears it is an issue with what is getting sent to the driver to start up, then please create a new ticket rather than continuing to comment here.

titusfortner on May 22, 2023

Thanks for info, i’ll try check the permissions on intelliJ and my user profile tomorrow

Auto81 on May 18, 2023

SeleniumManager is using same permissions as the user executing the Selenium test. It’s storing files in a directory under that user’s $HOME directory. I’m not sure which permissions are locked down that prevent it from working, and if we can find a way to address it we will, but Selenium Manager might not be able to solve this, and you might need to manage drivers by yourself.

titusfortner on May 18, 2023