[🐛 Bug]: Unable to close the browser driver and unable to do parallel run in ADO pipeline

[MonicaKannian]

What happened?

Chrome driver using selenium does not kill/close/quit properly. Which leads to the connectivity issue to the host for parallel execution

How can we reproduce the issue?

Yes, with respect to any pipeline execution chrome driver does not close

Relevant log output

OpenQA.Selenium.WebDriverException: An unknown exception was encountered sending an HTTP request to the remote WebDriver server for URL.
The exception message was: No connection could be made because the target machine actively refused it.

Operating System

Windows 10

Selenium version

selenium 4.14.1

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

Chrome 123 to latest

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

chrome

Are you using Selenium Grid?

No

[github-actions[bot]]

@MonicaKannian, 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!

[github-actions[bot]]

Hi, @MonicaKannian. 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.