karma-runner/karma

karma || karma-chrome-launcher Does Not Respect 'captureTimeout'

Open

#2116 opened on May 5, 2016

View on GitHub
 (0 comments) (2 reactions) (0 assignees)JavaScript (11,918 stars) (1,703 forks)batch import
help wantedneeds: investigation

Description

Expected behavior

If Chrome is taking too long to launch, I am expecting that I can alter 'captureTimeout' to wait longer.

The default is suppose to be 60sec. but, karma retries ~500msecs.

Actual behavior

05 05 2016 19:03:13.421:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/ 05 05 2016 19:03:13.437:INFO [launcher]: Starting browser Chrome w/o security. 05 05 2016 19:03:14.042:ERROR [launcher]: Cannot start Chrome

Just not waiting long enough.

Enviroment Details

Windoze 7; slow box

  • Karma version (output of karma --version): 0,13.22

  • Relevant part of your karma.config.js file

    captureTimeout: 120000,
retryLimit: 4,
browsers: ['Chromeage'],
customLaunchers: {
  Chromeage: {
    base: 'Chrome',
    flags: ['--disable-web-security'],
    displayName: 'Chrome w/o security.'
  }
},

### Steps to reproduce the behaviour

1.
2.
3.

Contributor guide

Tech stack
javascript
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic knowledge of karma configurationunderstanding of browser launcher internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the karma chrome launcher code to see how `captureTimeout` is used. The issue suggests it is not being passed correctly or ignored. Look at the launcher's timing logic and compare with the default timeout (60s) and the observed retry interval (~500ms). Focus on files like `launcher.js`, `browser.js`, or the Chrome launcher plugin to identify where the timeout is applied. Consider whether the timeout is being reset incorrectly or overwritten.