When a wdio-*-service throws a SevereServiceError, chromedriver does not shut down cleanly.

[jamesmortensen]

I have observed that when wdio services throw a SevereServiceError, chromedriver hangs and does not shut down.

$ lsof -i :9515
COMMAND    PID USER   FD   TYPE            DEVICE SIZE/OFF NODE NAME
chromedri 8993  jem    6u  IPv4 0x641c20f71e7938b      0t0  TCP localhost:9515 (LISTEN)
chromedri 8993  jem    7u  IPv6 0x641c20f69be5c13      0t0  TCP localhost:9515 (LISTEN)

If the processes are not killed, the next time WebdriverIO is started, it fails since port 9515 is blocked:

Starting ChromeDriver 89.0.4389.23 (61b08ee2c50024bab004e48d2b1b083cdbdac579-refs/branch-heads/4389@{#294}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
[1621021673.016][SEVERE]: bind() failed: Address already in use (48)
IPv4 port not available. Exiting...

It would help if chromedriver shuts down properly when there is a severe error in another service requiring the test runner to stop.