Karma always disconnects Chrome while CONFIGURING

I upgraded to node 17, and now Karma tests won't run anymore, with node 16 they worked fine but now it seems Chrome is not able to configure anymore, because it always disconnects during the CONFIGURING part:

17 03 2022 13:03:57.251:DEBUG [karma-server]: A browser has connected on socket 5oDGuMCmOC3c73hcAAAB
17 03 2022 13:03:57.253:DEBUG [web-server]: upgrade /socket.io/?EIO=4&transport=websocket&sid=raqoNWSxu2VpgM5UAAAA
17 03 2022 13:03:57.267:DEBUG [Chrome Headless 96.0.4664.93 (Windows 10)]: undefined -> CONNECTED
17 03 2022 13:03:57.268:INFO [Chrome Headless 96.0.4664.93 (Windows 10)]: Connected on socket 5oDGuMCmOC3c73hcAAAB with id 69979605
17 03 2022 13:03:57.268:DEBUG [launcher]: BEING_CAPTURED -> CAPTURED
17 03 2022 13:03:57.269:DEBUG [launcher]: ChromeHeadless (id 69979605) captured in 3.014 secs
17 03 2022 13:03:57.269:DEBUG [Chrome Headless 96.0.4664.93 (Windows 10)]: CONNECTED -> CONFIGURING
17 03 2022 13:04:27.269:WARN [Chrome Headless 96.0.4664.93 (Windows 10)]: Disconnected (0 times) , because no message in 30000 ms.
Chrome Headless 96.0.4664.93 (Windows 10) ERROR
Disconnected , because no message in 30000 ms.
17 03 2022 13:04:27.270:DEBUG [Chrome Headless 96.0.4664.93 (Windows 10)]: CONFIGURING -> DISCONNECTED
17 03 2022 13:04:27.270:WARN [framework.snapshot]: Snapshot data is unavailable
17 03 2022 13:04:27.271:DEBUG [launcher]: CAPTURED -> BEING_KILLED
17 03 2022 13:04:27.271:DEBUG [launcher]: BEING_KILLED -> BEING_FORCE_KILLED
17 03 2022 13:04:27.271:DEBUG [Chrome Headless 96.0.4664.93 (Windows 10)]: DISCONNECTED -> DISCONNECTED

Reproduce the Karma test failure with Node 17 and Chrome Headless, then compare the same setup on Node 16. Start by tracing the browser's CONFIGURING phase and the 30-second disconnect shown in the logs; done means Chrome Headless completes configuration and the Karma tests run successfully on Node 17.

Written by the indexing model from the issue text.