since version 131.0.6778.69, got the error : disconnected: not connected to DevTools

[Nana]

Hi,

I'm using Chrome for testion with Selenium.

Since Stable version updated to 131.0.6778.69, I get this random error:

disconnected: not connected to DevTools (failed to check if window was closed: disconnected: not connected to DevTools) (Session info: chrome=131.0.6778.69) Build info: version: '4.18.1', revision: 'b1d3319b48' System info: os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.13' Driver info: org.openqa.selenium.chrome.ChromeDriver Command: [47bd7226d5cf80f1c35690ad7bfff1b8, getCurrentUrl {}] Capabilities {acceptInsecureCerts: false, browserName: chrome, browserVersion: 131.0.6778.69, chrome: {chromedriverVersion: 131.0.6778.69 (77e2244bbcda..., userDataDir: C:\Windows\SystemTemp\scope...}, fedcm:accounts: true, goog:chromeOptions: {debuggerAddress: localhost:57364}, networkConnectionEnabled: false, pageLoadStrategy: normal, platformName: windows, proxy: Proxy(), se:cdp: ws://localhost:57364/devtoo..., se:cdpVersion: 131.0.6778.69, 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}

Nothing has changes in my testing environment.

Does someone get the same error?

Thanks and regards

[clifmo]

Yes, this arrived in Stable overnight tonight for us. It was in dev stream all last month. We assumed it would be fixed.

[Nana]

Hi,

Thanks for you answer. Hope this will be fixed very quickly. don't know if there is a bug about it