Message 95029 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	pitrou
Recipients	pitrou
Date	2009年11月08日.00:00:37
SpamBayes Score	0.00043251438
Marked as misclassified	No
Message-id	<1257638440.73.0.268077668125.issue7282@psf.upfronthosting.co.za>

Content
When you use an RLock from a thread which wasn't created through the high-level `threading` API (but, for example, using thread.start_new_thread()), the RLock creates a DummyThread object by calling current_thread(), and that DummyThread is immortal (as well as its attributes etc.). This implementation wart can easily lead to reference leaks for unsuspecting users. One simple solution is not to call current_thread() in RLock, but use get_ident() instead. Patch attached.

Content

When you use an RLock from a thread which wasn't created through the
high-level `threading` API (but, for example, using
thread.start_new_thread()), the RLock creates a DummyThread object by
calling current_thread(), and that DummyThread is immortal (as well as
its attributes etc.). This implementation wart can easily lead to
reference leaks for unsuspecting users.
One simple solution is not to call current_thread() in RLock, but use
get_ident() instead. Patch attached.

History
Date	User	Action	Args
2009年11月08日 00:00:40	pitrou	set	recipients: + pitrou
2009年11月08日 00:00:40	pitrou	set	messageid: <1257638440.73.0.268077668125.issue7282@psf.upfronthosting.co.za>
2009年11月08日 00:00:38	pitrou	link	issue7282 messages
2009年11月08日 00:00:38	pitrou	create

homepage