Fixes #12289 - Improve ConcurrentPool concurrency. #12290
Merged
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.
A call to
sweep()
, although protected by the lock for concurrent calls toreserve()
, may be concurrent withremove(Entry)
.remove(Entry)
in turn callsentries.remove(Object)
, so that the concurrent iteration insweep()
overentries
fails with anArrayIndexOutOfBoundsException
.Now using the bulk
entries.removeIf(Predicate)
method insweep()
, so that sweeping is atomic with respect toentries.remove(Object)
.