Skip to content

Consider regions that lead to very small back paddings as unsuitable #71

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 10, 2022

Conversation

phil-opp
Copy link
Member

If the resulting back padding is too small to be stored as a hole, we treat the hole as unsuitable for the allocation. This way, we avoid unrecoverable leaks of that back padding, which can add up over time and fragment the heap.

Fixes #66

@phil-opp phil-opp marked this pull request as draft October 10, 2022 07:40
If the resulting back padding is too small to be stored as a hole, we treat the hole as unsuitable for the allocation. This way, we avoid unrecoverable leaks of that back padding, which can add up over time and fragment the heap.
@phil-opp phil-opp force-pushed the dont-leak-back-padding branch from 538ab1c to 14d25f9 Compare October 10, 2022 08:31
@phil-opp phil-opp force-pushed the dont-leak-back-padding branch from 14d25f9 to c24a6b9 Compare October 10, 2022 09:12
@phil-opp phil-opp marked this pull request as ready for review October 10, 2022 09:12
@phil-opp phil-opp merged commit d1cd084 into main Oct 10, 2022
@phil-opp phil-opp deleted the dont-leak-back-padding branch October 10, 2022 09:45
phil-opp added a commit that referenced this pull request Oct 10, 2022
@phil-opp
Copy link
Member Author

Published as v0.10.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Memory leak
1 participant