-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Karma doesn't clean up Socket.IO listeners when exiting #2980
Closed
briandipalma opened this issue
Apr 23, 2018
· 0 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Closed
Karma doesn't clean up Socket.IO listeners when exiting #2980
briandipalma opened this issue
Apr 23, 2018
· 0 comments
· May be fixed by Omrisnyk/npm-lockfiles#122 or Omrisnyk/npm-lockfiles#132
Comments
briandipalma
added a commit
to briandipalma/karma
that referenced
this issue
Apr 23, 2018
Not removing Socket.IO listeners can cause memory issues in long running processes that spawn many Karma instance. Fixes karma-runner#2980
briandipalma
added a commit
to briandipalma/karma
that referenced
this issue
Apr 24, 2018
Not removing Socket.IO listeners can cause memory issues in long running processes that spawn many Karma instance. Fixes karma-runner#2980
briandipalma
added a commit
to briandipalma/karma
that referenced
this issue
May 3, 2018
Not removing Socket.IO listeners can cause memory issues in long running processes that spawn many Karma instance. Fixes karma-runner#2980
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Karma should clean up resources when exiting.
Actual behaviour
It doesn't.
Environment Details
karma --version
): 2.0.0karma.config.js
fileSteps to reproduce the behaviour
Server
afterServer
PR incoming, just needed a GitHub issue.
The text was updated successfully, but these errors were encountered: