dispose of previous inner (in-memory) cache when calling ClearAll() #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 fixes a memory leak happens upon calling ClearAll() on InMemoryCache instances.
I had a concern that some classes will hold the reference of the previous cache and that the disposing will cause in certain edge race cases a serious exception (AlreadyDisposedException).
But using the dispose cache object is ok, but does nothing and no exception as well.
Set: will not set, as if the ClearAll was called a nanosecond after setting
Get: will get nothing, as if the ClearAll was called a nanosecond before getting