Expected behaviour

The behaviour as to when to kill the browser should be configurable. There is a hardcoded value in karma/lib/launchers/process.js which is var killTimeout = 2000

Actual behaviour

Since the value is not configurable the browser gets killed after 2s. If there's something running within the browser (e.g. when using karma-coverage and istanbul works on a large number of files), it gets killed.

Environment Details

• Karma version (output of karma --version): 1.3.0
• Relevant part of your karma.config.js file: not available

Steps to reproduce the behaviour

1. Configure karma-coverage to run on a big code base
2. Run karma
3. Observe how the browser gets killed after 2s before it has a chance to finish processing the coverage data