[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

Gregory P. Smith added the comment: r78519 r78520 for py3k and 3.1. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

Gregory P. Smith added the comment: fixed in trunk r78517 and release26-maint r78518. still needs merging into py3k and release31-maint -- resolution: -> accepted ___ Python tracker __

[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

Changes by Nir Aides : -- nosy: +nirai ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/ma

[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

Antoine Pitrou added the comment: I can reproduce it under Linux using "ulimit -Su 2600". (deselecting 2.5 as it doesn't receive bug fixes anymore) -- nosy: +gps, jyasskin, pitrou priority: -> normal stage: -> needs patch versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5

[issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

New submission from John Mark Schofield : SUMMARY: When you attempt to start a thread, and you're unable to (you get thread.error) it leaves a thread stuck in an "initial" state that never exits. (threading.enumerate() shows the threads and lists their status as "initial.") REPRODUCTION STEPS: S