selenium: [๐ Bug]: Unable to run a test because driver cannot connect to DevTools
What happened?
Iโm having an issue when trying to run my enterprise end to end tests. It was working well and it is no more the case, I canโt understand why. The same test work for my collegues.
Iโve created a small code to reproduce quickly the issue that is not link to any professional data.
Iโm currently using Unbuntu 22.04.4 LTS, Google Chrome 126.0.6478.126 and the matching chrome driver downloaded by Selenium.
ls -al ~/.cache/selenium/chromedriver/linux64
total 12
drwxrwxr-x 3 pirquessa pirquessa 4096 juil. 10 14:24 .
drwxrwxr-x 3 pirquessa pirquessa 4096 juil. 10 14:24 ..
drwxrwxr-x 2 pirquessa pirquessa 4096 juil. 10 14:24 126.0.6478.126
When I run ruby ./driver.rb, I get an error linked to connection with DevTools:
#0 0x637232177c7a <unknown>: disconnected: Unable to receive message from renderer (Selenium::WebDriver::Error::WebDriverError)
(failed to check if window was closed: disconnected: not connected to DevTools)
How can we reproduce the issue?
Here is my `driver.rb` to reproduce the issue:
require 'selenium-webdriver'
driver = Selenium::WebDriver.for(:chrome)
driver.get 'https://selenium.dev'
driver.quit
### Relevant log output
```shell
#0 0x637232177c7a <unknown>: disconnected: Unable to receive message from renderer (Selenium::WebDriver::Error::WebDriverError)
(failed to check if window was closed: disconnected: not connected to DevTools)
(Session info: chrome=126.0.6478.126)
from #1 0x637231e5ae2c <unknown>
from #2 0x637231e421a6 <unknown>
from #3 0x637231e41d85 <unknown>
from #4 0x637231e3fcc6 <unknown>
from #5 0x637231e401ca <unknown>
from #6 0x637231e3ede1 <unknown>
from #7 0x637231e46b43 <unknown>
from #8 0x637231e3eb14 <unknown>
from #9 0x637231e41a4d <unknown>
from #10 0x637231e3fcc6 <unknown>
from #11 0x637231e401ca <unknown>
from #12 0x637231e3ede1 <unknown>
from #13 0x637231e35f08 <unknown>
from #14 0x637231e3eb14 <unknown>
from #15 0x637231e3e3a2 <unknown>
from #16 0x637231e3de3b <unknown>
from #17 0x637231e5d172 <unknown>
from #18 0x637231e2f5bf <unknown>
from #19 0x637231e2f09f <unknown>
from #20 0x637231ed6e5d <unknown>
from #21 0x637231eca363 <unknown>
from #22 0x637231e9a247 <unknown>
from #23 0x637231e9ab9e <unknown>
from #24 0x63723213e24b <unknown>
from #25 0x6372321422f1 <unknown>
from #26 0x637232129afe <unknown>
from #27 0x637232142e52 <unknown>
from #28 0x63723210e79f <unknown>
from #29 0x637232167638 <unknown>
from #30 0x637232167810 <unknown>
from #31 0x637232176dac <unknown>
from #32 0x7bebd6894ac3 <unknown>
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/response.rb:55:in `assert_ok'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/response.rb:34:in `initialize'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/http/common.rb:101:in `new'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/http/common.rb:101:in `create_response'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/http/default.rb:103:in `request'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/http/common.rb:67:in `call'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/bridge.rb:635:in `execute'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/remote/bridge.rb:76:in `create_session'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/common/driver.rb:323:in `block in create_bridge'
from <internal:kernel>:90:in `tap'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/common/driver.rb:322:in `create_bridge'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/common/driver.rb:73:in `initialize'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/chrome/driver.rb:35:in `initialize'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/common/driver.rb:47:in `new'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver/common/driver.rb:47:in `for'
from /home/pirquessa/.rbenv/versions/3.3.4/lib/ruby/gems/3.3.0/gems/selenium-webdriver-4.22.0/lib/selenium/webdriver.rb:89:in `for'
from ./driver.rb:4:in `<main>'
Operating System
Unbuntu 22.04.4 LTS
Selenium version
Ruby 3.3.4
What are the browser(s) and version(s) where you see this issue?
Google Chrome 126.0.6478.126
What are the browser driver(s) and version(s) where you see this issue?
Auto downloaded by Selenium ? Identified as 126.0.6478.126
Are you using Selenium Grid?
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (4 by maintainers)
Okay, I found the solution. If you launch it in headful you can see itโs asking the user to select the default search engine, blocking the test from executing. This behaviour can be disabled with the option
--disable-search-engine-choice-screenHereโs a full config that works for me:
Iโd suggest to make this the default in the selenium_chrome_headless driver