[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Martin Panter added the comment: The change to the test seems to have the desired effect. The buildbots are no longer timing out (tests are failing for other reasons). -- resolution: -> fixed stage: commit review -> resolved status: open -> closed _

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Roundup Robot added the comment: New changeset 613196986c09 by Martin Panter in branch '2.7': Issue #26456: Force all child threads to terminate in TestForkInThread https://hg.python.org/cpython/rev/613196986c09 -- nosy: +python-dev ___ Python tracker

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Serhiy Storchaka added the comment: But please add a reference to this issue. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Zachary Ware added the comment: I can confirm that child-exit.patch fixes the immediate issue, so I'm +1 on just committing it since it will make several buildbots useful again. Improving general handling of the situation can be done in a new issue. For the record, I agree that this seems to

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Martin Panter added the comment: Yes it looks like you might be right about those hanging buildbots. The occasional successes (e.g. ) seem to happen when test_thread runs before any of the TK, TCL, a

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Zachary Ware added the comment: I suspect this may be what causes several of the 2.7 builders to fail. The ones that fail look like they complete successfully, but then sit with no output until buildbot kills them. For example: http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO%202

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Martin Panter added the comment: I should point out that I think this problem didn’t used to happen. As far as I know, it could be a bug in a recently upgraded glibc or something. On another Linux computer I cannot produce the problem. When I get a chance I will try upgrading packages to see i

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

Changes by Serhiy Storchaka : -- nosy: +pitrou, serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26456] import _tkinter + TestForkInThread leaves zombie with stalled thread

New submission from Martin Panter: After running the 2.7 test suite many times, my Linux OS’s memory slowly gets eaten up. It seems to be because of zombie Python processes that never get cleaned up unless I kill them explicitly. I never get this problem with the Python 3 test suite. I narrow