[issue13778] Python should invalidate all non-owned 'thread.lock' objects when forking

lesha report at bugs.python.org
Fri Jan 13 10:33:04 CET 2012


lesha <pybug.20.lesha at xoxy.net> added the comment:

Actually, I think it does not matter which thread owns the lock, it is still invalid to try to acquire a lock that was grabbed by the fork() parent. Why? Because the fork() parent cannot free the child's copy of the lock anyway, and it's guaranteed to be dead also.

----------

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


More information about the Python-bugs-list mailing list