Fix memory leak with nackCountLogs #386
Merged
+51
−0
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.
Description
nackCountLogswasn't getting cleaned up properly ingenerator_interceptor.gofrom the nack package.this is fixed in two ways:
UnbindRemoteStream()can delete the respectivenackCountLogsfor the providedSSRC.loop()we can drop thenackCountLogsmap if it's empty. This is particularly helpful if a lot of them get accumulated over time.Reference issue
#328 and @joeturki mentioned that there were reports of a memory leak so hopefully this fixes it.