Michael Felt <mich...@felt.demon.nl> added the comment: 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, Michael Sent from my iPhone > On 12 Jan 2018, at 23:48, Serhiy Storchaka <rep...@bugs.python.org> wrote: > > > Serhiy Storchaka <storchaka+cpyt...@gmail.com> 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 <rep...@bugs.python.org> > <https://bugs.python.org/issue32542> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue32542> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
