Add check to avoid underflow in memory manager #4351
Merged
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.
Which issue does this PR close?
Part of #4328
What changes are included in this PR?
Included a check to avoid underflow when available memory is calculated when consumers request additional memory.
The trackers acquire memory independent of
MemoryManager
and communicates the memory acquired using the functiongrow_tracker_usage
. The tracker can end up allocating more memory than what is defined inMemoryManager.pool_size
This PR does not prevent trackers from allocating more memory than what is defined inMemoryManager.pool_size
. Might be a candidate for future refactoring.Are these changes tested?
Added a test to avoid underflow.