[issue1183] race in SocketServer.ForkingMixIn.collect_children

Changes by Jeffrey Yasskin: -- status: pending -> closed __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1183] race in SocketServer.ForkingMixIn.collect_children

David Ripton added the comment: The "if pid not in self.active_children: continue" check that was added in r61106 appears to fix the bug, so I'm happy. Thanks. __ Tracker <[EMAIL PROTECTED]> __ __

[issue1183] race in SocketServer.ForkingMixIn.collect_children

Jeffrey Yasskin added the comment: Hmm. I think the race can only happen if you call collect_children() concurrently from multiple threads or from a signal handler. The waidpid(0) bug (which affected anyone who spawned subprocesses from anything other than ForkingMixIn) is partly fixed by r61106,

[issue1183] race in SocketServer.ForkingMixIn.collect_children

David Ripton added the comment: Just noticed that this is a partial duplicate of issue 1540386. -- versions: +Python 2.5 __ Tracker <[EMAIL PROTECTED]> __ _

[issue1183] race in SocketServer.ForkingMixIn.collect_children

David Ripton added the comment: No signal handler. Yes, we run subprocesses. I don't believe either is necessary to trigger the race condition, though. __ Tracker <[EMAIL PROTECTED]> __ _

[issue1183] race in SocketServer.ForkingMixIn.collect_children

Ralf Schmitt added the comment: I've had the exact same error - but only when I used a subclass of XMLRPCServer, which installed signal handlers for SIGCHLD (which then called collect_children). Does your code install such a signal handler? (I found mine somewhere on the web). Do you start any su

[issue1183] race in SocketServer.ForkingMixIn.collect_children

Changes by Sean Reifschneider: -- keywords: +patch priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Uns

[issue1183] race in SocketServer.ForkingMixIn.collect_children

New submission from David Ripton: CentOS Linux 5, Python 2.4.3 (but code appears unchanged in 2.5 and trunk, so I don't believe this bug has already been fixed) We have an xmlrpc server that subclasses DocXMLRPCServer.DocXMLRPCServer and SocketServer.ForkingMixIn. Under load, it sometimes cras