{"action":"opened","issue":{"url":"https://api.github.com/repos/mochajs/mocha/issues/1683","labels_url":"https://api.github.com/repos/mochajs/mocha/issues/1683/labels{/name}","comments_url":"https://api.github.com/repos/mochajs/mocha/issues/1683/comments","events_url":"https://api.github.com/repos/mochajs/mocha/issues/1683/events","html_url":"https://github.com/mochajs/mocha/issues/1683","id":73177813,"number":1683,"title":"Large test suite just stops running","user":{"login":"KJTsanaktsidis","id":1418177,"avatar_url":"https://avatars.githubusercontent.com/u/1418177?v=3","gravatar_id":"","url":"https://api.github.com/users/KJTsanaktsidis","html_url":"https://github.com/KJTsanaktsidis","followers_url":"https://api.github.com/users/KJTsanaktsidis/followers","following_url":"https://api.github.com/users/KJTsanaktsidis/following{/other_user}","gists_url":"https://api.github.com/users/KJTsanaktsidis/gists{/gist_id}","starred_url":"https://api.github.com/users/KJTsanaktsidis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KJTsanaktsidis/subscriptions","organizations_url":"https://api.github.com/users/KJTsanaktsidis/orgs","repos_url":"https://api.github.com/users/KJTsanaktsidis/repos","events_url":"https://api.github.com/users/KJTsanaktsidis/events{/privacy}","received_events_url":"https://api.github.com/users/KJTsanaktsidis/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-05T01:59:53Z","updated_at":"2015-05-05T01:59:53Z","closed_at":null,"body":"We're using Mocha and Karma to run a large (~4000 tests) suite in Chrome. Recently, however, we have been unable to run the entire test suite. The suite simply stops after a certain number of tests have been run, with no error. Eventually a warning is logged that no communication has been received after 240 seconds.\r\n\r\nI've attached an image of a chrome CPU profile showing what happens at the end of the test run. The call stack becomes unbelievably nested, with huge amounts of time being spent inside mocha `run`, `callFn`, and `done`. Eventually mocha just refuses to run any further tests, represented by the cliff at the end of the profile run. The browser prints no errors about a stack overflow or similar though.\r\n\r\nAny suggestions as to what might be going on here?\r\n\r\n![screen shot 2015-05-05 at 11 54 26 am](https://cloud.githubusercontent.com/assets/1418177/7465971/1f334e3a-f31e-11e4-846c-bf2863628595.png)\r\n\r\nThe chrome CPU profile can be downloaded from https://dl.dropboxusercontent.com/u/24050078/CPU-20150505T115402.cpuprofile"}}