Skip to content
This repository has been archived by the owner on Sep 25, 2020. It is now read-only.

unref() has a memory leak; don't use it #239

Merged
merged 2 commits into from
Feb 2, 2016
Merged

Conversation

jwolski
Copy link
Contributor

@jwolski jwolski commented Feb 1, 2016

@Raynos
Copy link
Contributor

Raynos commented Feb 1, 2016

lgtm.

@@ -299,5 +299,6 @@ test('emits ringpop error on canceled request', function t(assert) {
});

client.scanForWedgedRequests();
client.destroy();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

unref'ing also wound up hiding a potentially hanging test.

@Raynos
Copy link
Contributor

Raynos commented Feb 1, 2016

cool.

@benfleis
Copy link
Contributor

benfleis commented Feb 1, 2016

@jwolski Sorry to have lead us down this rabbit hole. And I'm a bit sad that what I thought was really responsible turned out to have evil side effects...

jwolski pushed a commit that referenced this pull request Feb 2, 2016
unref() has a memory leak; don't use it
@jwolski jwolski merged commit def343e into master Feb 2, 2016
@jwolski jwolski deleted the no-unref-no-memory-leak branch February 2, 2016 06:36
@jwolski
Copy link
Contributor Author

jwolski commented Feb 2, 2016

@benfleis no problemo. these things keep us on our toes!

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

Successfully merging this pull request may close these issues.

3 participants