[6.2] [Runtime] Properly deallocate extended storage for conformance cache entries #80887
Conversation
This file contains hidden or 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
(cherry picked from commit d576fa3)
… free list This memory is part of the conformance cache concurrent hash map, so when we clear the conformance cache, record each of the allocated pointers within the concurrent map's free list. This way, it'll be freed with the rest of the concurrent map when it's safe to do so. (cherry picked from commit 885f829)
|
@swift-ci please test |
nkcsgexi
approved these changes
Apr 17, 2025
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.
dlopenor similar. Keep track of these allocations in a list, and move them over to the concurrent free list in the conformance cache when clearing the cache, so they will eventually be deallocated.