Assert acount hash mmap file capacity > 0 #33575
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.
Problem
We are seeing a memory allocation failure when writing 0 to the end of
account's hash file.
It seems that it could be caused by self.capacity = 0. When we estimate the
capacity, it is possible that self.capacity = 0.
However, if
write()
is called, self.capacity must be greater than 0.Summary of Changes
To rule out the possiblity, add an "assert" for capacity must be greater than
0.
Fixes #