[issue6721] Locks in python standard library should be sanitized on fork

Antoine Pitrou report at bugs.python.org
Tue May 3 02:21:00 CEST 2011


Antoine Pitrou <pitrou at free.fr> added the comment:

I encountered this issue while debugging some multiprocessing code; fork() would be called from one thread while sys.stdout was in use in another thread (simply because of a couple of debugging statements). As a result the IO lock would be already "taken" in the child process and any operation on sys.stdout would deadlock.

This is definitely something that can happen more easily than I thought.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6721>
_______________________________________


More information about the Python-bugs-list mailing list