Andrew added the comment: Gregory P. Smith,
"if you are seeing a memory leak and the statements that fail before the gc.enable call are more than" The problem in my case was different. It was race condition between gc.isenabled and gc.disable. Isenabled was called when gc was disabled by another subprocess. This caused that later on gc.enable was not triggered. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27448> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
