fix memory leak when creating streams that already exist (#3) #40
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bug Description
When creating a stream via
CreateStream(), a new stream is always created even if a stream with the sameidalready exists, causing a memory leak where goroutines are created viastr.run()but never closed.How to Read This PR
This PR fixes that bug by closing the newly created stream if the stream
idis found in the server's map of streams.How to Test This PR
These changes are reflected in the tests, but there is a potential race condition where the newly created stream might not have been closed by the time the test checks whether
runtime.NumGoroutine()is equal tonumGoRoutines.At the moment I can't think of a better, simple way to test this so if you'd prefer to not have an imperfect test in
server_test.go, let me know and I will remove it. Thanks!