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 Michael.Felt
Recipients Michael.Felt, serhiy.storchaka
Date 2018-01-15.01:56:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Thanks for the clarification. 

Being curious, is there a way to see what the size of the cache is? I want to believe, but i do not have the impression memory is being reallocated to later users. My gut feeling is that the code change permits repeated calls to a function in a way that it reuses memory it received before (rather than a memory leak of repeatedly allocating a brand new buffer). What I expected, more accurately hoped for, is that cache was either freed and/or made available for reuse. 

Since I am on my phone atm I am less successful at finding documentation. I would be very grateful for a link to the relevant information and I’ll look further, time permitting. Thx again,


Sent from my iPhone

> On 12 Jan 2018, at 23:48, Serhiy Storchaka <> wrote:
> Serhiy Storchaka <> added the comment:
> Issue25582 fixed a memory leak. If run the tests repeatedly every iteration leaked 100 MB of memory. If you get a MemoryError with a single iteration, this means that your machine just doesn't have enough memory for tests. Tests require around 500-600MB of memory on 32-bit platform.
> ----------
> nosy: +serhiy.storchaka
> _______________________________________
> Python tracker <>
> <>
> _______________________________________
Date User Action Args
2018-01-15 01:56:41Michael.Feltsetrecipients: + Michael.Felt, serhiy.storchaka
2018-01-15 01:56:41Michael.Feltlinkissue32542 messages
2018-01-15 01:56:39Michael.Feltcreate