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 tim.peters
Recipients Esa.Peuha, brian.curtin, pitrou, r.david.murray, tim.golden, tim.peters, vstinner, Пётр.Дёмин
Date 2013-10-14.17:56:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381773385.08.0.121330975385.issue19246@psf.upfronthosting.co.za>
In-reply-to
Content
@haypo, this has nothing to do with PyMalloc.  As I reported in my first message, only 7 PyMalloc arenas are in use at the end of the program, less than 2 MB total.  *All* other arenas ever used were released to the OS.

And that's not surprising.  The vast bulk of the memory used in the test case isn't in small objects, it's in *strings* of ever-increasing size.  Those are gotten by many calls to the system malloc().
History
Date User Action Args
2013-10-14 17:56:25tim.peterssetrecipients: + tim.peters, pitrou, vstinner, tim.golden, r.david.murray, brian.curtin, Esa.Peuha, Пётр.Дёмин
2013-10-14 17:56:25tim.peterssetmessageid: <1381773385.08.0.121330975385.issue19246@psf.upfronthosting.co.za>
2013-10-14 17:56:25tim.peterslinkissue19246 messages
2013-10-14 17:56:24tim.peterscreate