[issue32542] memory not freed, aka memory leak continues...

Michael Felt added the comment: Not an issue in 3.9, so, closing: "not relevant" -- stage: -> resolved status: open -> closed ___ Python tracker ___

[issue32542] memory not freed, aka memory leak continues...

STINNER Victor added the comment: ctypes test cases tearDown() may always clear _pointer_type_cache. Would it help? -- nosy: +vstinner ___ Python tracker

[issue32542] memory not freed, aka memory leak continues...

Serhiy Storchaka added the comment: > Being curious, is there a way to see what the size of the cache is? len(_pointer_type_cache)? -- ___ Python tracker

[issue32542] memory not freed, aka memory leak continues...

Michael Felt 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

[issue32542] memory not freed, aka memory leak continues...

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

[issue32542] memory not freed, aka memory leak continues...

New submission from Michael Felt : in issue25582 - the issue is not (yet) resolved. Perhaps this one can be closed and issue25582 reopened. Both from python2-2.7.14 and "git master" I am getting: michael@x071:[/data/prj/python/git/gcc-python3-3.7]./python -m unittest -v