-
Notifications
You must be signed in to change notification settings - Fork 50
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
Do not extend the pool on each allocation #55
base: develop
Are you sure you want to change the base?
Conversation
10969c8
to
e231843
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #55 +/- ##
===========================================
- Coverage 93.71% 93.69% -0.03%
===========================================
Files 9 9
Lines 589 587 -2
===========================================
- Hits 552 550 -2
Misses 37 37
Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebase on current develop for a full CI suite run.
Reported in Boost mailing list: https://lists.boost.org/Archives/boost/2023/06/254750.php Commit 951ca57 changed malloc_need_resize() to use set_next_size(), which sets start_size in addition to setting next_size. this causes repeated use of purge_memory() to allocate 2x size after every use. Fixes boostorg#54
Rebased. |
The failure is due to quota limit on codecov, unrelated to my change. |
Reported in Boost mailing list: https://lists.boost.org/Archives/boost/2023/06/254750.php
Commit 951ca57 changed malloc_need_resize() to use set_next_size(), which sets start_size in addition to setting next_size. this causes repeated use of purge_memory() to allocate 2x size after every use.
Fixes #54