v5.2 - Resolve memory leak in arcache #117
Merged
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
If the write miss thread local cache was enabled, a mistake existed in the case where the write thread is under high pressure which could lead to memory being leaked. Nodes are now wrapped in a safe wrapper to ensure they can not be leaked.
Firstyear
force-pushed
the
20240615-memory-leak
branch
from
efef0c4 to
4486563
Compare
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.
If the write miss thread local cache was enabled, a mistake existed in the case where the write thread is under high pressure which could lead to memory being leaked. Nodes are now wrapped in a safe wrapper to ensure they can not be leaked.