based on https://ci.angularjs.org/job/angular.js-igor-testacular/584/console

this is my interpretation of what happened:

If a browser launched by Testacular is taking a long time to start and a startup timeout is reached, Testacular will kill it. If however, between the kill command is issued and the browser is actually killed the browser connects, Testacular will hang.

• T starts
• T launches a browser B
• B is taking a long time to start and doesn't get captured before startup time is reached
• T issues a process kill command (kill might not be immediate - e.g. when relayed via a shell script like we do with ie.sh)
• B gets finally captured
• B gets finally killed by the kill command
• T sees that browser disconnect and process exit and it then just waits and waits