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 vstinner
Recipients ezio.melotti, michael.foord, pitrou, rbcollins, serhiy.storchaka, vstinner
Date 2015-04-01.12:39:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
By the way, a workaround is also to run each test (file) in a new fresh process. It's a common way to work around memory fragmentation ;-)

> On some machines with limited resources this can cause multiple MemoryErrors.

Do you have an idea of the memory usage of the Python test suite? You may run it with tracemalloc to get the memory peak from tracemalloc.get_traced_memory()[1].

I mean, memory is cheap nowadays. If you get MemoryError, it's probably more a bug than tests leaking more and more memory, no?
Date User Action Args
2015-04-01 12:39:17vstinnersetrecipients: + vstinner, pitrou, rbcollins, ezio.melotti, michael.foord, serhiy.storchaka
2015-04-01 12:39:17vstinnersetmessageid: <>
2015-04-01 12:39:17vstinnerlinkissue23839 messages
2015-04-01 12:39:17vstinnercreate