Selenium Grid 4.11.0 and Chrome Browser 115.0.5790.171

218 views

Skip to first unread message

Raju Thomas

unread,

Aug 10, 2023, 10:34:43 AM8/10/23

to Selenium Users

Hi All,

After updating grid hub and node to 4.11.0 and chrome browser 115.0.5790.171, we are getting timeout error

Caused by: org.openqa.selenium.ScriptTimeoutException: Timed out waiting for driver server to shutdown.

On nodes we have 4 max-sessions configured. After a test a completed the test call driver.quit() but we see that chrome browser process ID are still running. That leads to 100% CPU usage after 30 mins of running is suite 500 testcases and thereafter no new browser session are available and shutdown of browser times out. Below is the log from a node.

I am not sure why there are many chrome PID in task manager even though only 4 browser sessions are active.

Is it a bug in selenium grid 4.11.0 or chrome driver?

Is there is way to address this issue?

************** Node Logs **************

4:56:48.431 INFO [LocalNode.newSession] - Session created by the Node. Id: 9b730d8db61ba27917045191c63bd183, Caps: Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 115.0.5790.171, ch:options: {executionId: fed11ee3-9411-4768-84f7-36d..., recordVideo: false, site: connsbigcommerce, subscriptionKey: sd-010-01-01}, chrome: {chromedriverVersion: 115.0.5790.170 (cc0d30c2ca5..., userDataDir: C:\Windows\SystemTemp\scope...}, goog:chromeOptions: {debuggerAddress: localhost:53512}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: Windows XP, proxy: Proxy(), se:bidiEnabled: false, se:cdp: ws://192.0.1.13:5567/sessio..., se:cdpVersion: 115.0.5790.171, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: ignore, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:extension:minPinLength: true, webauthn:extension:prf: true, webauthn:virtualAuthenticators: true}
15:00:39.774 INFO [OsProcess.destroy] - Unable to drain process streams. Ignoring but the exception being swallowed follows.
org.apache.commons.exec.ExecuteException: The stop timeout of 2000 ms was exceeded (Exit value: -559038737)
at org.apache.commons.exec.PumpStreamHandler.stopThread(PumpStreamHandler.java:295)
at org.apache.commons.exec.PumpStreamHandler.stop(PumpStreamHandler.java:180)
at org.openqa.selenium.os.OsProcess.destroy(OsProcess.java:144)
at org.openqa.selenium.os.CommandLine.destroy(CommandLine.java:142)
at org.openqa.selenium.remote.service.DriverService.stop(DriverService.java:293)
at org.openqa.selenium.grid.node.config.DriverServiceSessionFactory$1.stop(DriverServiceSessionFactory.java:203)
at org.openqa.selenium.grid.node.DefaultActiveSession.execute(DefaultActiveSession.java:54)
at org.openqa.selenium.grid.node.local.SessionSlot.execute(SessionSlot.java:126)
at org.openqa.selenium.grid.node.local.LocalNode.executeWebDriverCommand(LocalNode.java:628)
at org.openqa.selenium.grid.node.ForwardWebDriverCommand.execute(ForwardWebDriverCommand.java:35)
at org.openqa.selenium.remote.http.Route$PredicatedRoute.handle(Route.java:384)
at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
at org.openqa.selenium.remote.tracing.SpanWrappedHttpHandler.execute(SpanWrappedHttpHandler.java:91)
at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:347)
at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
at org.openqa.selenium.grid.node.Node.execute(Node.java:262)
at org.openqa.selenium.remote.http.Route$CombinedRoute.handle(Route.java:347)
at org.openqa.selenium.remote.http.Route.execute(Route.java:69)
at org.openqa.selenium.remote.AddWebDriverSpecHeaders.lambda$apply$0(AddWebDriverSpecHeaders.java:35)
at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44)
at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
at org.openqa.selenium.remote.ErrorFilter.lambda$apply$0(ErrorFilter.java:44)
at org.openqa.selenium.remote.http.Filter$1.execute(Filter.java:63)
at org.openqa.selenium.netty.server.SeleniumHandler.lambda$channelRead0$0(SeleniumHandler.java:44)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
15:00:40.527 WARN [SpanWrappedHttpHandler.execute] - Unable to execute request: Timed out waiting for driver server to shutdown.
Build info: version: '4.11.0', revision: '040bc5406b'

Dhanalakota Abhishek

unread,

Jul 19, 2024, 7:05:24 AM7/19/24

to Selenium Users

Hi there,

I am encountering the same issue regarding Selenium grid, I have max_concurrent session = 8 but after a short time CPU usage is hitting 100 and failing the jobs.