#96 Fixes memory leak due to Oct 1st regression in processItems #99
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.
See #96
I ran the proof with two different versions of ristretto and got 2 different results.
This is definitely a regression.
Found the offending commit
d963fa2
Reading the diff I saw a logic change that looked like an error since
policy.Add
can, in some cases, returnvictims
whenadded
is false.https://github.com/dgraph-io/ristretto/blob/master/policy.go#L168
This commit extracts the for loop from the if statement, fixing the memory leak.
This change is