[New-bugs-announce] [issue7481] Failing to start a thread leaves "zombie" thread in "initial" state

John Mark Schofield report at bugs.python.org
Fri Dec 11 20:15:40 CET 2009


New submission from John Mark Schofield <jschofield at gmail.com>:

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: See attached file.

EXPECTED RESULT: Failing to start a thread should not leave the thread
in an un-executable state. I would expect the thread start to either
succeed or result in the thread being closed and GC'd.

VERIFIED ON:
Python 2.5.2 on OS X 10.5.8
Python 2.5.2 on Ubuntu 8.04
Python 2.5.4 on Windows XP Professional (Version 2002) SP3
Python 2.6.1 on OS X 10.6.2

----------
files: repro_case.py
messages: 96271
nosy: schof
severity: normal
status: open
title: Failing to start a thread leaves "zombie" thread in "initial" state
type: behavior
versions: Python 2.5, Python 2.6
Added file: http://bugs.python.org/file15527/repro_case.py

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue7481>
_______________________________________


More information about the New-bugs-announce mailing list