Skip to content
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

bug(websocket): memory leak when option 'ws:true' is used. #114

Merged
merged 1 commit into from
Sep 28, 2016

Conversation

chimurai
Copy link
Owner

fixes #113

@coveralls
Copy link

coveralls commented Sep 26, 2016

Coverage Status

Coverage increased (+0.04%) to 96.914% when pulling e4f8da7 on ws-memory-leak into 4db1bfa on master.

@chimurai chimurai changed the title bug(websocket): fix memory leak when option 'ws:true' is used. bug(websocket): memory leak when option 'ws:true' is used. Sep 26, 2016
Copy link

@julbra julbra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chimurai This fixes the leak in my tests. Thank you!

@chimurai chimurai merged commit 2bf1f93 into master Sep 28, 2016
@chimurai chimurai deleted the ws-memory-leak branch September 28, 2016 22:10
@chimurai
Copy link
Owner Author

Fix is shipped in v0.17.2

Thanks for reporting the issue. Appreciate all the effort @julbra !

@julbra
Copy link

julbra commented Sep 30, 2016

Excellent, glad to be of help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak (ws: true)
3 participants