Chromium

I feel that I have encountered the same issue. Updating both google-chrome-stable and chromedriver to v128 returns the following error

session not created: Chrome failed to start: exited normally.
  (session not created: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /opt/google/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)

However, downgrading back to v127 for both google-chrome-stable and chromedriver fixes this issue.

It seems like Chromedriver is using random webports now, causing the session creation to fail.
Nice breaking feature Dev team ;-)
Adding  --port=9515 to the DriverParams solved the problem.
I am now able tu use both Chrome and Chromedriver v128.

This change is intentional -- https://chromium.googlesource.com/chromium/src/+/6f33d75f071e322c4a3e49b0a4ac2022e5b6cada

The question is how does one programmatically retrieve this randomly assigned port?

Randomly our pipelines are unable to talk to Selenium The HTTP request to the remote WebDriver server for URL http://selenium.com:4444n timed out after 120 seconds. ---> System.Net.WebException: The request was aborted: The operation has timed out.

Even though we have updated ChromeDriver version to latest.

Do anyone has any feedback which I can implement? All my testers are using below chromeoptions, still encountering stability issues

                chromeOptions.AddArgument("--start-maximized");
                chromeOptions.AddArgument("--window-size=1920,1080");
                chromeOptions.AddArgument("lang=en-GB");
                chromeOptions.AddArgument("--disable-gpu");
                chromeOptions.AddArgument("--incognito");
                chromeOptions.AddArgument("--disable-web-security");
                chromeOptions.AddArgument("disable-dev-shm-usage");
                chromeOptions.AddArgument("--proxy-auto-detect");

With Autoit I use the following OPTION and CAPABILITIES succesfully:

        _WD_Option('Driver', 'chromedriver.exe')
        _WD_Option('Port', 9515)
        _WD_Option('DriverParams', '--port=9515 --verbose --log-path="' & @ScriptDir & '\chrome.log"')

; create capabilites for session
        _WD_CapabilitiesStartup()
        _WD_CapabilitiesAdd('alwaysMatch', 'chrome')
        _WD_CapabilitiesAdd('w3c', True)
        _WD_CapabilitiesAdd('excludeSwitches', 'enable-automation')
       _WD_CapabilitiesAdd("args","disable-search-engine-choice-screen")
        Local $sCapabilities = _WD_CapabilitiesGet()

The functions I use are part of the Autoit Webdriver UDF, maintained by Autoit forum member Danp2.
After adding --port=9515 Chromedriver was working again as expected. You must implement this is your own programming language.

As your busy already Adding _WD_CapabilitiesAdd("args","disable-search-engine-choice-screen") disables the choose searchengine question at every startup.
Please implement also in your own programming language :-)

Good luck.