-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Chrome 110: Cannot start session #11721
Comments
@adambeth, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@adambeth - What happens when you try using |
Also, we run tests on that version and they work. |
Hi, @adambeth. Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue. Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough. Reply to this issue when all information is provided, thank you. |
Sorry for not providing more info, I obviously didn't read the template
correctly
Upgrading the Selenium version did not make a difference
macOS 13.2.1
Java 17
testng: 7.7.0
Here is how the driver is set up
System.out.println("LOOKING FOR DRIVER");
System.setProperty("webdriver.chrome.driver", "./chromedriver");
System.out.println("DRIVER FOUND");
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless");
options.addArguments("user-agent=GetMyBoat/Test");
setupDriver = new ChromeDriver(options);
setupDriver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));
The URL /HTML I cannot share the, unfortunately, but it shouldn't matter as
it never gets passed drive instantiation
setupDriver = new ChromeDriver(options);
So I suppose you can use any URL or HTML you want
…On Wed, Mar 1, 2023 at 2:15 PM github-actions[bot] ***@***.***> wrote:
Hi, @adambeth <https://github.com/adambeth>.
Please follow the issue template, we need more information to reproduce
the issue.
Either a complete code snippet and URL/HTML (if more than one file is
needed, provide a GitHub repo and instructions to run the code), the
specific versions used, or a more detailed description to help us
understand the issue.
Note: If you cannot share your code and URL/HTML, any complete code
snippet and URL/HTML that reproduces the issue is good enough.
Reply to this issue when all information is provided, thank you.
—
Reply to this email directly, view it on GitHub
<#11721 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOOWKBF7K7PUEVSTDPO3WZ44WRANCNFSM6AAAAAAVL645YE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I suppose now that I read the template this might be a better bug for the
Chrome repo?
…On Wed, Mar 1, 2023 at 2:41 PM Adam Bethlehem ***@***.***> wrote:
Sorry for not providing more info, I obviously didn't read the template
correctly
Upgrading the Selenium version did not make a difference
macOS 13.2.1
Java 17
testng: 7.7.0
Here is how the driver is set up
System.out.println("LOOKING FOR DRIVER");
System.setProperty("webdriver.chrome.driver", "./chromedriver");
System.out.println("DRIVER FOUND");
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless");
options.addArguments("user-agent=GetMyBoat/Test");
setupDriver = new ChromeDriver(options);
setupDriver.manage().timeouts().implicitlyWait(Duration.ofSeconds(10));
The URL /HTML I cannot share the, unfortunately, but it shouldn't matter
as it never gets passed drive instantiation
setupDriver = new ChromeDriver(options);
So I suppose you can use any URL or HTML you want
On Wed, Mar 1, 2023 at 2:15 PM github-actions[bot] <
***@***.***> wrote:
> Hi, @adambeth <https://github.com/adambeth>.
> Please follow the issue template, we need more information to reproduce
> the issue.
>
> Either a complete code snippet and URL/HTML (if more than one file is
> needed, provide a GitHub repo and instructions to run the code), the
> specific versions used, or a more detailed description to help us
> understand the issue.
>
> Note: If you cannot share your code and URL/HTML, any complete code
> snippet and URL/HTML that reproduces the issue is good enough.
>
> Reply to this issue when all information is provided, thank you.
>
> —
> Reply to this email directly, view it on GitHub
> <#11721 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHICOOWKBF7K7PUEVSTDPO3WZ44WRANCNFSM6AAAAAAVL645YE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Either here or in the Chrome/ChromeDriver one, you need to provide an exact way to reproduce the issue. |
System.out.println("LOOKING FOR DRIVER");
System.setProperty("webdriver.chrome.driver", "./chromedriver");
System.out.println("DRIVER FOUND");
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless");
options.addArguments("user-agent=GetMyBoat/Test");
setupDriver = new ChromeDriver(options);
…On Wed, Mar 1, 2023 at 2:50 PM Diego Molina ***@***.***> wrote:
Either here or in the Chrome/ChromeDriver one, you need to provide an
exact way to reproduce the issue.
—
Reply to this email directly, view it on GitHub
<#11721 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOOU4PVJ3SCX7D6TDX2LWZ5AYFANCNFSM6AAAAAAVL645YE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The exact way to run the code with the version I supplied, Im not sure how
else I should show you
…On Wed, Mar 1, 2023 at 2:52 PM Adam Bethlehem ***@***.***> wrote:
System.out.println("LOOKING FOR DRIVER");
System.setProperty("webdriver.chrome.driver", "./chromedriver");
System.out.println("DRIVER FOUND");
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless");
options.addArguments("user-agent=GetMyBoat/Test");
setupDriver = new ChromeDriver(options);
On Wed, Mar 1, 2023 at 2:50 PM Diego Molina ***@***.***>
wrote:
> Either here or in the Chrome/ChromeDriver one, you need to provide an
> exact way to reproduce the issue.
>
> —
> Reply to this email directly, view it on GitHub
> <#11721 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHICOOU4PVJ3SCX7D6TDX2LWZ5AYFANCNFSM6AAAAAAVL645YE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I am asking for that because we use the most recent Chrome and ChromeDriver in our pipelines and code examples from the documentation on the 3 operating systems and we do not have that error. I just launched one test and it worked. |
I understand why you are asking, but I have no more information
Can you not even tell me what the error means
[1677674781.237][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
There is nothing on the web about it
…On Wed, Mar 1, 2023 at 2:57 PM Diego Molina ***@***.***> wrote:
I am asking for that because we use the most recent Chrome and
ChromeDriver in our pipelines and code examples from the documentation on
the 3 operating systems and we do not have that error. I just launched one
test and it worked.
—
Reply to this email directly, view it on GitHub
<#11721 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOOT4CYB5ZCQCPFXOYN3WZ5BVBANCNFSM6AAAAAAVL645YE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@adambeth - That error usually indicates a non compatible combo of a chrome browser and a chromedriver being found. Can you please do the following:
➜ 110.0.5481.77 ./chromedriver
Starting ChromeDriver 110.0.5481.77 (65ed616c6e8ee3fe0ad64fe83796c020644d42af-refs/branch-heads/5481@{#839}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
curl -X POST 'localhost:9515/session' \
--header 'Content-Type: application/json; charset=utf-8' \
--data-raw '{ "desiredCapabilities": { "browserName": "chrome", "goog:chromeOptions": { "args": [ "--remote-debugging-port=9225" ] }, "goog:loggingPrefs": { "browser": "ALL", "driver": "ALL", "server": "ALL" } }, "capabilities": { "browserName": "chrome" } }' If you don't see a browser spawn up then we can for sure conclude that the problem lies in the |
@krishan thanks I don't see a browser spawn but my chrome version and
driver version are the correct ones
What repo do I log a ticker for chrome driver issues, please? Im using the
latest chrome driver and the latest version of chrome so not sure what
other version to use as you cant stop chrome from updating to the
latest version
…On Fri, Mar 3, 2023 at 6:33 AM Krishnan Mahadevan ***@***.***> wrote:
@adambeth <https://github.com/adambeth> - That error usually indicates a
non compatible combo of a chrome browser and a chromedriver being found.
Can you please do the following:
1. Start the chromedriver that you are using by running ./chromedriver.
You should see something like this
➜ 110.0.5481.77 ./chromedriver
Starting ChromeDriver 110.0.5481.77 (65ed616c6e8ee3fe0ad64fe83796c020644d42af-refs/branch-heads/5481@{#839}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
1. Now try to create a new session by running the below curl command.
The expectation is that you should see a new browser spin off
curl -X POST 'localhost:9515/session' \
--header 'Content-Type: application/json; charset=utf-8' \
--data-raw '{ "desiredCapabilities": { "browserName": "chrome", "goog:chromeOptions": { "args": [ "--remote-debugging-port=9225" ] }, "goog:loggingPrefs": { "browser": "ALL", "driver": "ALL", "server": "ALL" } }, "capabilities": { "browserName": "chrome" } }'
If you don't see a browser spawn up then we can for sure conclude that the
problem lies in the chromedriver binary that you are using.
—
Reply to this email directly, view it on GitHub
<#11721 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHICOOTN45EXA7XXB3VRIFDW2FYCTANCNFSM6AAAAAAVL645YE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi, @adambeth. You can see if the feature is passing in the Web Platform Tests. If it is something new, please create an issue with the ChromeDriver team. |
Hi, @adambeth. You can see if the feature is passing in the Web Platform Tests. If it is something new, please create an issue with the ChromeDriver team. |
I am still having issues with this. I got
When I run my app, I got this:
How to fix? I also tried with latest Selenium version but it does not work
|
Hi there. Same issue here. A Chrome window spawns, but in blank, with the address "data:," in it. Code written in Python, running in windows 10. My code is:
The output (console):
and, after a looooong while, the error message:
|
Check my fix here: |
Thanks, @riki95 , but can't use that solution. I'm in a corporate laptop, and Google Chrome (not chromium) is what it is installed. I used a workaround using Firefox driver instead, but I hope than in following versions this issue with Chrome should be fixed. |
Only after running chromedriver as sudo in terminal, was i able to get past the Using a selenium remote webdriver and connecting to a manually downloaded chromedriver, and running it as 'sudo', also allowed me to get past the Will need to find a way for SeleniumManager to open chromedriver with appropriate permissions, as it doesnt seem to be currently |
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. |
Thanks for info, i'll try check the permissions on intelliJ and my user profile tomorrow |
On Mac, my user account is in sudoers, and have tried setting owner/group to multiple different combinations I have set the SeleniumManager chromedriver, IntelliJ and Chrome to be owned by me, and tried the group first as wheel then root. None of these combos have helped, is there a specific combo they need to be?
|
@bonigarcia do you have any idea regarding this? |
This issue seems not related to Selenium Manager. Selenium Manager manages the driver, i.e., download, cache, and make drivers available to the bindings. That feature seems correct since chromedriver is correctly stored in the cache folder. The problem |
Does anyone have any solution? I'm still getting the same message: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 500. Message: disconnected: not connected to DevTools |
A horrible work around I found was running the test runner / IDE as sudo. But other than proving the concept of everything else being correct I really wouldnt recommend this method |
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. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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?
Relevant log output
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?
No
The text was updated successfully, but these errors were encountered: