New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IE11 disconnects after some time #8

mgol opened this Issue Jan 7, 2014 · 2 comments


None yet
2 participants

mgol commented Jan 7, 2014

My unit tests take much longer to run in IE than in Chrome/Firefox (where they take 30-40 seconds). After some time over 2 minutes IE11 gets disconnected:

.WARN [IE 11.0.0 (Windows 7)]: Disconnected

IE 11.0.0 (Windows 7): Executed 5 of 414 (skipped 178) DISCONNECTED (2 mins 30.3 45 secs / 1 min 30.916 secs)
Warning: Task "karma:jenkins" failed. Use --force to continue.

Aborted due to warnings.

This makes it impossible for me to test on IE... Is there anything else that could trigger the disconnection besides the timeout? Any way to troubleshoot it?

EDIT: it seems it's not based on time but on some specific tests. It almost always fails after 181 or 180 tests from 414. There is, however, nothing demanding in these particular tests that wasn't already run in earlier tests due to beforeEach blocks. If I exclude the offending module, tests fail after 9 minutes, near the end.

Why is it so? IMO the total disconnection should never happen. If there is a bug, an error should be thrown instead of just disconnecting from the browser which says nothing about what's wrong.


This comment has been minimized.


vojtajina commented Jan 20, 2014

Well, in IE, anything can happen. I did a tons of stuff to make IE (8-10) stable on our Travis + SL, however I didn't have any issues with IE11.

You can try canary Karma (0.11), which has these features. You can configure:
browserDisconnectTimeout (in ms, if a browser disconnects, Karma waits this timeout for reconnecting)
browserDisconnectTolerance (how many times Karma tries to restart the browser if it disconnects)

Are you using Jasmine? If so, can you try jasmine.DEFAULT_UPDATE_INTERVAL = 0; in some of your files? Then you should be able to track which test does it.


This comment has been minimized.

mgol commented Jan 20, 2014

Thanks. Yes, I'm using Jasmine so I'll try it, the browserDisconnectTolerance setting also seems promising. I'm not sure about the timeout since IE11 fails on these tests after non-consistent amount of time, it seems to depend more on specific tests (or set of tests) than on the time itself.

I'll report here with my findings.

christophercurrie pushed a commit to christophercurrie/karma-ie-launcher that referenced this issue Jan 22, 2014

Christopher Currie
Support 64-bit IE and isolate environment.
This patch tries to auto-detect 64-bit IE by checking
for the appropriate environment variables. It also
improves reliability of the tests by disabling
extensions and using "InPrivate" mode to ignore
existing user data. Addresses karma-runner#1, karma-runner#2, karma-runner#4, and possibly karma-runner#8.

milafrerichs added a commit to codeforamerica/city-analytics-dashboard that referenced this issue Aug 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment