Which Karma configuration prevents browser timeout during long-running test suites?

Karma orchestrates test execution by acting as a proxy server that communicates with browser launchers via WebSockets. In environments with large test suites or resource-constrained CI runners, the connection between the Karma server and the browser can drop before the full suite completes.

While singleRun determines whether the server shuts down after completion, there is uncertainty regarding the specific timeout thresholds that govern the browser's lifecycle and the socket connection stability during extended execution periods.

What configuration options are available to extend the browser disconnection timeout? Does Karma provide a mechanism to keep the browser instance alive if the test execution exceeds the default timeout window?