[issue20743] test_tcl memory leak

Antoine Pitrou added the comment: Ok, fixed now. -- resolution: -> invalid stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue20743] test_tcl memory leak

Roundup Robot added the comment: New changeset 00393de6919d by Antoine Pitrou in branch '2.7': Issue #20743: Fix a reference leak in test_tcl. http://hg.python.org/cpython/rev/00393de6919d -- ___ Python tracker ___

[issue20743] test_tcl memory leak

Roundup Robot added the comment: New changeset 38a06e411698 by Antoine Pitrou in branch '3.3': Issue #20743: Fix a reference leak in test_tcl. http://hg.python.org/cpython/rev/38a06e411698 New changeset 10b1f60a72fa by Antoine Pitrou in branch 'default': Issue #20743: Fix a reference leak in tes

[issue20743] test_tcl memory leak

Serhiy Storchaka added the comment: LGTM. There is a little related but more complex issue1524639. -- assignee: -> pitrou stage: needs patch -> commit review ___ Python tracker ___

[issue20743] test_tcl memory leak

Changes by Antoine Pitrou : -- components: +Tests priority: high -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue20743] test_tcl memory leak

Antoine Pitrou added the comment: Actually, this looks mostly like a cleanup issue in the tests. Following patch seems to solve it: diff --git a/Lib/test/test_tcl.py b/Lib/test/test_tcl.py --- a/Lib/test/test_tcl.py +++ b/Lib/test/test_tcl.py @@ -376,6 +376,7 @@ class TclTest(unittest.TestCase)

[issue20743] test_tcl memory leak

Antoine Pitrou added the comment: This actually appeared with 89b738e3d0c9, i.e. it's not a regression but an existing leak that was uncovered by a new test. -- ___ Python tracker _

[issue20743] test_tcl memory leak

New submission from Antoine Pitrou: Witnessed on 2.7, 3.3, 3.4: $ ./python -m test -uall -R3:3 test_tcl [1/1] test_tcl beginning 6 repetitions 123456 .. test_tcl leaked [12, 12, 12] references, sum=36 test_tcl leaked [5, 5, 5] memory blocks, sum=15 -- components: Library (Lib), Tki