Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Repeatedly disconnected from Chrome (mac)

See original GitHub issue

Chrome recently updated on my mac, and I’m now running Chrome 44.0.2403 (Mac OS X 10.10.3) and have Karma v0.13.3. Sometimes all of my tests will run, but they start breaking when the test runner disconnects from Chrome:

Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 14 of 218 SUCCESS (0 secs / 0.248 secs)
23 07 2015 09:49:14.059:WARN [Chrome 44.0.2403 (Mac OS X 10.10.3)]: Disconnected (1 times
Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 14 of 218 DISCONNECTED (10.082 secs / 0.248
Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 15 of 218 DISCONNECTED (10.082 secs / 1.015
Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 16 of 218 DISCONNECTED (10.082 secs / 1.026
Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 17 of 218 DISCONNECTED (10.082 secs / 1.063
Chrome 44.0.2403 (Mac OS X 10.10.3): Executed 18 of 218 DISCONNECTED (10.082 secs / 1.082

Issue Analytics

State:
Created 8 years ago
Comments:10 (2 by maintainers)

Top GitHub Comments

4reactions

bchernycommented, Apr 15, 2016

EDIT: The fix that worked for me was to add browserDisconnectTolerance: 10 to the karma.conf (any number >1 works)

Same issue - but running chrome in the foreground does not help.

Versions:

OSX: 10.10.5
node: 4.2.4
karma: 0.13.22
karma-chrome-launcher: 0.2.3
karma-jasmine: 0.3.8
jasmine-core: 2.4.1

I’ve tried:

Heap profile during tests (results are normal)
xdescribeing tests - If I xdescribe any 30 (of our ~1500) tests, the suite passes

karma.conf.coffee:

module.exports = (config) ->
  config.set
    frameworks: [ "jasmine" ]
    files: [...]  # ~500 files
    exclude: [...]
    preprocessors: {
      '**/*.js': ['sourcemap']
    }
    reporters: ['mocha']
    mochaReporter:
      ignoreSkipped: yes
      autowatch: yes
    port: 9292
    colors: process.platform is 'darwin'
    logLevel: config.LOG_INFO
    autoWatch: true
    reportSlowerThan: 200
    browsers: ['Chrome']
    browserNoActivityTimeout: 100000
    captureTimeout: 60 * 1000
    singleRun: true
    captureConsole: true
    useIframe: false
    restartOnFileChange: true

0reactions

dcrockwellcommented, Apr 29, 2016

The solution posted by @bcherny seems to at least suppress the error, but the output is still quite funky:

PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 11 of 11 SUCCESS (0.077 secs / 0.015 secs)
Safari 9.0.3 (Mac OS X 10.11.3): Executed 11 of 11 SUCCESS (0.074 secs / 0.012 secs)
Chrome 50.0.2661 (Mac OS X 10.11.3): Executed 11 of 11 SUCCESS (0.075 secs / 0.017 secs)
Firefox 42.0.0 (Mac OS X 10.11.0): Executed 11 of 11 SUCCESS (0.1 secs / 0.011 secs)
TOTAL: 44 SUCCESS
DEBUG [karma]: Run complete, exiting.
DEBUG [launcher]: Disconnecting all browsers
DEBUG [framework.browserify]: cleaning up
PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 11 of 11 SUCCESS (0.077 secs / 0.015 secs)
Safari 9.0.3 (Mac OS X 10.11.3): Executed 11 of 11 DISCONNECTED (10.093 secs / 0.012 secs)
PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 11 of 11 SUCCESS (0.077 secs / 0.015 secs)
Safari 9.0.3 (Mac OS X 10.11.3): Executed 11 of 11 DISCONNECTED (10.093 secs / 0.012 secs)
Chrome 50.0.2661 (Mac OS X 10.11.3): Executed 11 of 11 DISCONNECTED (10.094 secs / 0.017 secs)
Firefox 42.0.0 (Mac OS X 10.11.0): Executed 11 of 11 SUCCESS (0.1 secs / 0.011 secs)
INFO [karma]: Restarting Chrome 50.0.2661 (Mac OS X 10.11.3) (1 of 10 attempts)