Fix a bug in sync caches where memory usage kept increasing when the eviction listener is set (v0.9.x) #296
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.
This PR fixes a bug in
sync::Cache
andsync::SegmentedCache
, which causes eviction listener's key-level locks not to be removed after sending notifications. This happened only when theImmediate
notification delivery mode is used for the eviction listener. (It is the default mode) Another mode,Queued
mode, is unaffected as it does not use the key locks.These key locks are stored in an internal
moka::cht::SegmentedHashMap
withArc<K>
as their keys. So this bug caused theSegmentedHashMap
to hold all keysK
that has been inserted to the cache. It will continuously increasing memory usage until the cache is dropped.Tested the fix by adding a check to unit test if the
SegmentedHashMap
is empty after sending all notifications.