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 loewis
Recipients loewis, pitrou, sable
Date 2008-08-08.22:46:50
SpamBayes Score 0.00011487412
Marked as misclassified No
Message-id <1218235611.41.0.14254205748.issue3526@psf.upfronthosting.co.za>
In-reply-to
Content
I cannot quite see why the problem is serious: even though the memory is
not returned to the system, it will be swapped out to the swap file, so
it doesn't consume any real memory (just swap space).

I don't think Python should integrate a separate malloc implementation.
Instead, Python's own memory allocate (obmalloc) should be changed to
directly use the virtual memory interfaces of the operating system (i.e.
mmap), bypassing the malloc of the C library.

So I'm -1 on this patch.
History
Date User Action Args
2008-08-08 22:46:51loewissetrecipients: + loewis, pitrou, sable
2008-08-08 22:46:51loewissetmessageid: <1218235611.41.0.14254205748.issue3526@psf.upfronthosting.co.za>
2008-08-08 22:46:50loewislinkissue3526 messages
2008-08-08 22:46:50loewiscreate