fix(ext/runtime): rollback memory count #645 #646
Merged
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
When allocate, allocate_uninitialized, or reallocate exceeded the memory limit, the count was incremented but never rolled back on failure. This caused all future allocations to fail permanently, even small legitimate ones.
nyannyacha
approved these changes
Nov 27, 2025
Contributor
|
Thank you! @max-lt |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When allocate, allocate_uninitialized, or reallocate exceeded the memory
limit, the count was incremented but never rolled back on failure. This
caused all future allocations to fail permanently, even small legitimate
ones.
What kind of change does this PR introduce?
Bug fix for #645