Antoine Pitrou <pit...@free.fr> added the comment: Why do you think PyObject_CallObject() is the culprit? There could be any number of reasons for a memory leak: - cyclic references needing to be cleared (have you tried calling PyGC_Collect()?) - reference leak(s) in your own internal logic - inefficiencies in the Windows memory allocator which mean "freed" memory is not necessarily reclaimed
PyObject_CallObject() itself is called with the GIL held, so the multithreaded nature of the program shouldn't be a factor. I would also suggest running more iterations, to see whether memory consumption reaches a stable state or grows endlessly. ---------- nosy: +pitrou _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8368> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
