This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients OO O, davin, paul.moore, pitrou, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2018-04-09.16:01:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523289687.41.0.682650639539.issue32759@psf.upfronthosting.co.za>
In-reply-to
Content
This change looks safe to me. I was just not sure that it is enough for practical cases. What if after allocating a large buffer the rest of the new area would be used for allocating small buffers? They can keep references to the large area after freeing the large buffer. Perhaps it is worth to block marking the remainder of a large area available. This will increase the memory consumption by small percent, but will reduce the risk of prolonging the life time of large blocks.
History
Date User Action Args
2018-04-09 16:01:27serhiy.storchakasetrecipients: + serhiy.storchaka, paul.moore, pitrou, tim.golden, zach.ware, steve.dower, davin, OO O
2018-04-09 16:01:27serhiy.storchakasetmessageid: <1523289687.41.0.682650639539.issue32759@psf.upfronthosting.co.za>
2018-04-09 16:01:27serhiy.storchakalinkissue32759 messages
2018-04-09 16:01:27serhiy.storchakacreate