[🐛 Bug]: Session still exists in Selenium Grid after Disposing RemoteWebDriver

[MJB222398]

What happened?

I have a Docker Selenium Grid and am using a RemoteWebDriver to run stuff on it. I am seeing that when I call RemoteWebDriver.Dispose() and then make an API call to get the Grid status (http://localhost:4444/status) that the session can sometimes (depending on how fast) still be seen here in the response.

Does disposing the driver not wait for the session to be properly terminated?

Command used to start Selenium Grid with Docker (or Kubernetes)

var driver = new RemoteWebDriver(
    new Uri("http://localhost:4444/wd/hub"),
    new ChromeOptions().ToCapabilities(),
    TimeSpan.FromSeconds(300));

driver.Dispose();
using var response = await new HttpClient().GetAsync("http://localhost:4444/status");
var content = await response.Content.ReadAsStringAsync();

Can see the session in this content

Relevant log output

Node logs

17:21:59.427 INFO [LocalNode.newSession] - Session created by the Node. Id: f5198aa622c0481cefd9b7d47fa2c764, Caps: Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 131.0.6778.108, chrome: {chromedriverVersion: 131.0.6778.87 (ce31cae94873..., userDataDir: /home/seluser/selenium/profile}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:45497}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: linux, proxy: Proxy(), se:bidiEnabled: false, se:cdp: ws://localhost:4444/session..., se:cdpVersion: 131.0.6778.108, se:containerName: chrome-node, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}
17:21:59.501 INFO [ProxyNodeWebsockets.createWsEndPoint] - Establishing connection to ws://localhost:45497/devtools/browser/5f199532-e648-4eb1-b702-b5477580a703
17:22:04.041 INFO [SessionSlot.stop] - Stopping session f5198aa622c0481cefd9b7d47fa2c764

Hub logs

17:22:04.043 INFO [LocalSessionMap.remove] - Deleted session from local Session Map, Id: f5198aa622c0481cefd9b7d47fa2c764
17:22:04.043 INFO [GridModel.release] - Releasing slot for session id f5198aa622c0481cefd9b7d47fa2c764

Operating System

Ubuntu 20.04

Docker Selenium version (image tag)

4.27.0-20241204

Selenium Grid chart version (chart version)

No response

[github-actions]

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

[VietND96]

I think this will be fixed in DotNet binding - SeleniumHQ/selenium#14624

[MJB222398]

I am not so sure, I am not using ChromeDriverService. And besides this issue happens for Firefox too.

[diemol]

This works as intended because the code responsibility in a remote session is to send the session termination command. It is up to the remote Grid (it could be a cloud provider, an Appium server, etc.) to terminate the session and release the resources.

If the code waits until the remote service stops everything, it could block the user from doing other local cleanup tasks or getting the next test ready.

[github-actions]

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.