Skip to content
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.

Fixed memory leak problem #160

Closed
wants to merge 1 commit into from
Closed

Fixed memory leak problem #160

wants to merge 1 commit into from

Conversation

yaoxp
Copy link

@yaoxp yaoxp commented Dec 7, 2016

When the nodes number is greater than 4, it will cause memory leaks.

When the node number is greater than 4, it will cause memory leaks.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.05%) to 76.288% when pulling 0561b19 on yaoxp:develop into 9b98410 on twitter:develop.

@kgoodier
Copy link
Contributor

kgoodier commented Dec 7, 2016

Did you find this by inspection or from debugging? This should have been fixed in change 5f9354a, there's even a unit test testAllStreamRemovalDoesNotLeak covering it. Or is there something else I'm missing?

Thanks!

@yaoxp
Copy link
Author

yaoxp commented Dec 7, 2016

I'm sorry I was wrong.
I use the master branch of the code. There is no problem in the develop branch.

@yaoxp yaoxp closed this Dec 7, 2016
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.

None yet

3 participants