Consider in-place realloc in memory usage statistics#4995
Open
GilesLeinad wants to merge 3 commits into
Open
Conversation
GilesLeinad
requested review from
TianlongLiang,
lum1n0us and
yamt
as code owners
July 14, 2026 09:34
GilesLeinad
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The memory usage statistics, which can be retrieved via the function
mem_allocator_get_alloc_info, do not consider in-place reallocations. The grow of the memory usage is only considered if a reallocation request is satisfied by a malloc, copy and free sequence. But it is not considered if the reallocation happens by extending the current node.