<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Dec 9, 2008, at 5:41 PM, Jean-Paul Calderone wrote:</div><blockquote type="cite"><div>On Tue, 9 Dec 2008 15:43:00 -0500, Phil Christensen <<a href="mailto:phil@bubblehouse.org">phil@bubblehouse.org</a>> wrote:<br><blockquote type="cite"><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">Everything is basically working, except for the fact that the md5sum processes never go away. It does seem that processEnded is being called, since that's what issues the callback on the deferred returned by run(), but the process sticks around, as a non-zombie, non-defunct process that still appears to be using small amounts of CPU time.</span></blockquote><br>processEnded shouldn't be called until the child has exited and been<br>reaped. This means that the md5sum process should not still exist in<br>any form if processEnded is being called. So either the processes you're<br>seeing aren't associated with the ProcessProtocol instances you think, or<br>there's a pretty serious bug in Twisted. :)<br></div></blockquote></div><div><br></div><div>Well, it looks like I was wrong, and the processes do go away, although they take awhile. This isn't that surprising, since I'm seeing 10-15 md5 processes happening in parallel, and they're checksumming relatively large (~150MB) WAV files. </div><div><br></div><div>It ended up being all because of a dumb mistake. Thanks for the help, though.</div><div><br></div><div>-phil</div></body></html>