Message 151556 - 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.

Author	glaubich
Recipients	glaubich
Date	2012-01-18.18:00:35
SpamBayes Score	2.7333286e-07
Marked as misclassified	No
Message-id	<1326909636.44.0.892345276723.issue13817@psf.upfronthosting.co.za>
In-reply-to

Content
Starting several threads, each just starting a subprocess.Popen and use communicate cause a deadlock in subprocess. (see attached file) I can only reproduce this with python 2.7.2, not with any other versions. 2.6.5, 2.6.7 and 3.2.2 are working fine. Also 2.4.6 is working, with a problem fixed by http://bugs.python.org/issue1731717. The attached script does not dead lock all the time, but at least every second call. I am on a linux x86_64. The python's are compiled by hand, except of 2.6.5.

Starting several threads, each just starting a subprocess.Popen and use communicate cause a deadlock in subprocess. (see attached file)

I can only reproduce this with python 2.7.2, not with any other versions. 2.6.5, 2.6.7 and 3.2.2 are working fine. Also 2.4.6 is working, with a problem fixed by http://bugs.python.org/issue1731717.

The attached script does not dead lock all the time, but at least every second call.

I am on a linux x86_64. The python's are compiled by hand, except of 2.6.5.

History
Date	User	Action	Args
2012-01-18 18:00:36	glaubich	set	recipients: + glaubich
2012-01-18 18:00:36	glaubich	set	messageid: <1326909636.44.0.892345276723.issue13817@psf.upfronthosting.co.za>
2012-01-18 18:00:35	glaubich	link	issue13817 messages
2012-01-18 18:00:35	glaubich	create