Python deadlock using subprocess.popen and communicate
atherun at gmail.com
Fri Sep 23 16:58:07 CEST 2011
On Sep 23, 12:08 am, Chris Angelico <ros... at gmail.com> wrote:
> On Fri, Sep 23, 2011 at 3:59 PM, Nobody <nob... at nowhere.com> wrote:
> > It doesn't even
> You intrigue me, sir. Does it odd?
> What is the remainder of this aborted sentence?
That is odd, I also find it odd that it deadlocks the entire python
system, even threads that have nothing to do with the subprocess stop
working, the entire thing just stops. I may not have pasted the full
stack trace looking at it again, I'll double check in a few.
I was able to repro this on a tool I have the source for, when I
attach to it to debug visual studio tells me the threads are
deadlocked and the only stack trace I have available to me is a low
level os call to a WriteFile function.
More information about the Python-list