[issue1739118] Investigated ref leak report related to thread regrtest.py

2009-10-30 Thread Hirokazu Yamamoto
Hirokazu Yamamoto ocean-c...@m2.ccsnet.ne.jp added the comment: This issue seems to be fixed in r75958. -- resolution: - duplicate status: open - closed superseder: - memory leaks in py3k ___ Python tracker rep...@bugs.python.org

[issue1739118] Investigated ref leak report related to thread regrtest.py

2009-05-10 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Hmm, rather than some C code in the internals, couldn't we simply iterate over the registered Thread objects and join() on those which are still running? -- nosy: +pitrou ___ Python tracker

[issue1739118] Investigated ref leak report related to thread(regrtest.py -

2009-04-06 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: Attaching Hirokazu's tests and experimental patch as plaintext. -- keywords: +patch nosy: +ajaksu2 stage: - patch review type: - resource usage Added file: http://bugs.python.org/file13628/test_leak.py

[issue1739118] Investigated ref leak report related to thread regrtest.py

2009-04-06 Thread Daniel Diniz
Changes by Daniel Diniz aja...@gmail.com: -- title: Investigated ref leak report related to thread(regrtest.py - - Investigated ref leak report related to thread regrtest.py Added file: http://bugs.python.org/file13629/experimental.patch ___ Python