[🐛 Bug]: Selenium 4.8.0 | Chrome 109 | Timed out waiting for driver server to stop

[nainighai-iqa]

What happened?

We are seeing high failures in test runs, due to Timed out waiting for the driver server to stop. These started coming from Chrome 109, hence we upgraded from selenium 4.6.0 to 4.8.0, As per Selenium 4.8.0 release (https://www.selenium.dev/blog/2023/selenium-4-8-0-released/), it supports chromerdriver v107, v108 and v109.

We are on Selenium 4.8.0 and JDK 11. The box we are using is of very high configuration, and the CPU utilization and Memory utilization are low even with 60+ threads.

Error Info: Skip reason due to test failure as: Timed out waiting for driver server to stop. Build info: version: '4.8.0', revision: '267030adea' System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.15.1' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [9e8713ab697f632b5fa48a464fa67d11, quit {}] Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 109.0.5414.120, chrome: {chromedriverVersion: 109.0.5414.74 (e7c5703604da..., userDataDir: C:\Program Files (x86)\scop...}, goog:chromeOptions: {debuggerAddress: localhost:58415}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:58415/devtoo..., se:cdpVersion: 109.0.5414.120, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true} Session ID: 9e8713ab697f632b5fa48a464fa67d11

How can we reproduce the issue?

Run with multiple threads with Selenium 4.8.0 and Chrome 109

Relevant log output

Error Info:
Skip reason due to test failure as: Timed out waiting for driver server to stop. Build info: version: '4.8.0', revision: '267030adea' System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.15.1' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [9e8713ab697f632b5fa48a464fa67d11, quit {}] Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 109.0.5414.120, chrome: {chromedriverVersion: 109.0.5414.74 (e7c5703604da..., userDataDir: C:\Program Files (x86)\scop...}, goog:chromeOptions: {debuggerAddress: localhost:58415}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:58415/devtoo..., se:cdpVersion: 109.0.5414.120, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true} Session ID: 9e8713ab697f632b5fa48a464fa67d11

Operating System

Windows, MAC

Selenium version

Selenium 4.8.0, JDK 11

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

Chrome 109 (109.0.5414.120)

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

chromedriverVersion: 109.0.5414.74 (Downloaded by Selenium Manager under .cache folder)

Are you using Selenium Grid?

No

[github-actions[bot]]

@nainighai-iqa, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

Does this happen only when using Chrome 109? What happens if you use Chrome 108?

[nainighai-iqa]

We did not face this issue with Chrome 107 with Selenium 4.6.0.

[diemol]

What about Chrome 107/108 with Selenium 4.8.0?

[nainighai-iqa]

We have not tried that, because chrome upgraded, from 107 to 109, and then as per the selenium 4x release, we upgraded from 4.6.0 to 4.8.0

[nainighai-iqa]

### With Selenium 4.6.0 and Chrome 109: We observed, it was trying to establish a connection with 107 chromedriver and in the parallel run, many tests failed with errors in establishing the connection. The issue is also reproducible with 5 threads and at times with a single thread.

### With Selenium 4.8.0 and Chrome 109: Today, we tried with again one more parallel execution with 30 threads (parallel browser sessions). Out of 1710 test methods, 1592 tests failed due to Could not start a new session. Response code 500. Message: unknown error: DevToolsActivePort file doesn't exist Host info: host: 'XXXXXXXXXX01', ip: 'XXX.XXX.XXX.XX' Build info: version: '4.8.0', revision: '267030adea' System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.15.1' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [null, newSession {capabilities=[Capabilities {browserName: chrome, goog:chromeOptions: {args: [--ignore-certificate-errors, --test-type, --disable-extensions, --disable-infobars, --disable-save-password-bubble, --enable-geolocation, --start-maximized, --disable-notifications, --disable-component-update, --no-sandbox, --disable-dev-shm-usage, --safebrowsing-disable-down..., --safebrowsing-disable-exte...], extensions: [], prefs: {download.default_directory: D:\xxxxxxxxxxxxx\xxxxxxx..., download.prompt_for_download: false, profile.content_settings.exceptions.automatic_downloads..setting: 1, safebrowsing.enabled: false}}}], desiredCapabilities=Capabilities {browserName: chrome, goog:chromeOptions: {args: [--ignore-certificate-errors, --test-type, --disable-extensions, --disable-infobars, --disable-save-password-bubble, --enable-geolocation, --start-maximized, --disable-notifications, --disable-component-update, --no-sandbox, --disable-dev-shm-usage, --safebrowsing-disable-down..., --safebrowsing-disable-exte...], extensions: [], prefs: {download.default_directory: D:\xxxxxxxxxxxxx\xxxxxxx..., download.prompt_for_download: false, profile.content_settings.exceptions.automatic_downloads..setting: 1, safebrowsing.enabled: false}}}}].

It ended up in many stale chrome.exe and chromedriver.exe sessions and took CPU utilization to 100%. When we killed all these sessions, the CPU utilization came down to 10%.

[diemol]

This seems to be an issue in Chrome/ChromeDriver.

https://bugs.chromium.org/p/chromedriver/issues/detail?id=4331 https://bugs.chromium.org/p/chromedriver/issues/detail?id=4333 https://bugs.chromium.org/p/chromedriver/issues/detail?id=4343

Please follow updates on the first link.

[github-actions[bot]]

Hi, @nainighai-iqa. This issue has been determined to require fixes in ChromeDriver.

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. Feel free to comment the issues that you raise back in this issue. Thank you.

[achavva]

Hi all, I am facing the same issue.....any help please? Selenium 4.6.0 Java 17 Chrome browser 110

[nainighai-iqa]

Downgrade Selenium to 4.6.0, Chrome to 107 and suppress chrome updates.

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: achavva @.> Sent: Saturday, February 18, 2023 8:15:49 PM To: SeleniumHQ/selenium @.> Cc: Naini Ghai @.>; Mention @.> Subject: Re: [SeleniumHQ/selenium] [🐛 Bug]: Selenium 4.8.0 | Chrome 109 | Timed out waiting for driver server to stop (Issue #11627)

Hi all, I am facing the same issue.....any help please? Selenium 4.6.0 Java 17 Chrome browser 110

— Reply to this email directly, view it on GitHubhttps://github.com/SeleniumHQ/selenium/issues/11627#issuecomment-1435692020, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWRBG4RYDZPHGHWGXZPD3STWYDOB3ANCNFSM6AAAAAAUUBDBAA. You are receiving this because you were mentioned.Message ID: @.***>

[achavva]

Sure I will try to do that, but it's a temporary fix right. Where can i get update on this fix?

Thanks for your time in replying.

On Sat, 18 Feb, 2023, 10:32 pm nainighai-iqa, @.***> wrote:

Downgrade Selenium to 4.6.0, Chrome to 107 and suppress chrome updates.

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: achavva @.> Sent: Saturday, February 18, 2023 8:15:49 PM To: SeleniumHQ/selenium @.> Cc: Naini Ghai @.>; Mention @.> Subject: Re: [SeleniumHQ/selenium] [🐛 Bug]: Selenium 4.8.0 | Chrome 109 | Timed out waiting for driver server to stop (Issue #11627)

Hi all, I am facing the same issue.....any help please? Selenium 4.6.0 Java 17 Chrome browser 110

— Reply to this email directly, view it on GitHub< https://github.com/SeleniumHQ/selenium/issues/11627#issuecomment-1435692020>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AWRBG4RYDZPHGHWGXZPD3STWYDOB3ANCNFSM6AAAAAAUUBDBAA>.

You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/SeleniumHQ/selenium/issues/11627#issuecomment-1435717485, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG4LIYJVQJFXRBOF5X2KNODWYD6A5ANCNFSM6AAAAAAUUBDBAA . You are receiving this because you commented.Message ID: @.***>

[ndtreviv]

I get the original error (Timed out waiting for driver server to stop - nothing about DevToolsActivePort) on Selenium 4.6.0, Java 17 and Chrome 108.

None of the issues linked in https://github.com/SeleniumHQ/selenium/issues/11627#issuecomment-1422445986 seem appropriate.

Is the current advice still to downgrade to Chrome 107?

[nainighai-iqa]

Yes, you are correct.

We still faced the issue with Selenium 4.6.0, 4.8.0, 4.8.1, and Chrome 107. As our daily regression runs were getting impacted and giving false failures due to "Timed out waiting for driver server to stop" issue, lastly, we downgraded to Selenium 3.141.59 and Boni Garcia (WebDriverManager).

It seems Selenium Manager will take more time to come over this issue.

[achavva]

Hi guys I waited quite long to get help but none... I resolved the issue by adding both driver.close() and driver.quit().... Not sure this is the actual solution but I got luck... Try urs all the best

[ndtreviv]

Hi guys I waited quite long to get help but none... I resolved the issue by adding both driver.close() and driver.quit().... Not sure this is the actual solution but I got luck... Try urs all the best

I was also already doing this to no avail, alas.

[lnataraj]

while the test is in progress I'm getting the same error with Selenium 4.3.0 and chrome driver 111. can anyone help me with the workaround or fixes?

[github-actions[bot]]

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.