Error: Process didn't end after 20000ms

[cjhow]

Issue Description:
Hello, I am currently facing an issue when using the Chromium driver to run scripts. The ChromeDriver process does not shut down properly, which then causes the Appium process to terminate. Could you advise how this can be resolved?

This issue only happens when I start two Chrome browsers at the same time using the Chromium Driver (with a specified port). If I only launch one browser, the process closes correctly without problems.

In addition, if the script does not perform too many actions (e.g., clicks, inputs), the issue does not occur either.

Environment:

• Appium Version: 3.0.2
• Chromium Driver Version: 2.0.2
• ChromeDriver Version: 141.0.7390.54

Capabilities:

{
    "newCommandTimeout": 0,
    "dontStopAppOnReset": true,
    "noReset": true,
    "fullReset": false,
    "automationName": "chromium",
    "platformName": "mac",
    "browserName": "chrome",
    "appium:chromedriverPort": 9222,
    "goog:chromeOptions": {
        "args": [
            "--disable-blink-features=AutomationControlled",
            "--no-sandbox",
            "--disable-dev-shm-usage"
        ]
    }
}

Error details:

/Users/usr/.appium/node_modules/appium-chromium-driver/node_modules/teen_process/lib/subprocess.js:279
reject(new Error(Process didn't end after ${timeout}ms (cmd: '${this.rep}')));
^
Error: Process didn't end after 20000ms (cmd: '/Users/usr/.appium/node_modules/appium-chromium-driver/node_modules/appium-chromedriver/chromedriver/mac/chromedriver-mac-arm64_v141.0.7390.54 --port=9222 --verbose')
at Timeout._onTimeout (/Users/usr/.appium/node_modules/appium-chromium-driver/node_modules/teen_process/lib/subprocess.js:279:16)
at listOnTimeout (node:internal/timers:608:17)
at processTimers (node:internal/timers:543:7)

[KazuCocoa]

Did you check the chromedriver log? appium:verbose and appium:logPath capabilities might help to investigate the reason in the chromedriver process.

[cjhow]

I checked the ChromeDriver logs and saw the following messages:

[31780:627989:1002/192045.089357:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[31857:628767:1002/192052.957756:VERBOSE1:chrome/updater/updater.cc:423] UpdaterMain (--wake) returned 0.
[31854:628763:1002/192053.066207:VERBOSE1:chrome/updater/app/app_wakeall.cc:67] /Users/usr/Library/Application Support/Google/GoogleUpdater/141.0.7390.54/GoogleUpdater.app/Contents/MacOS/GoogleUpdater --wake exited 0
[31854:628751:1002/192053.066706:VERBOSE1:chrome/updater/updater.cc:423] UpdaterMain (--wake-all) returned 0.
[31859:628771:1002/192102.971877:VERBOSE1:chrome/updater/updater.cc:423] UpdaterMain (--crash-handler) returned 0.
[31856:628755:1002/192102.974473:VERBOSE1:chrome/updater/updater.cc:423] UpdaterMain (--crash-handler) returned 0.
[31780:627989:1002/192138.589795:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
[31780:627989:1002/192316.900151:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
Trying to load the allocator multiple times. This is not supported.
[1759404316.936][INFO]: [729a3f572721d829d5ba5d68a939b069] COMMAND Quit {
}
[1759404316.991][INFO]: [729a3f572721d829d5ba5d68a939b069] RESPONSE Quit
[1759404316.991][DEBUG]: Log type 'driver' lost 0 entries on destruction
[1759404316.991][DEBUG]: Log type 'browser' lost 15 entries on destruction

I also noticed that when I set the capability appium:verbose, the Process didn't end after 20000ms does not appear anymore.

[KazuCocoa]

Hm, the verbose option simply if appium prints logs or not:

https://github.com/appium/appium-chromedriver/blob/4a36acc782f96f55f031271b48473e925357f49c/lib/chromedriver.js#L637-L640

[cjhow]

I just encountered this issue again after enabling verbose. However, when the issue occurred, I didn’t see any errors in the appium:logPath.