[issue31310] semaphore tracker isn't protected against crashes

[Antoine Pitrou]

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

> Thus, as the _pid argument is None in the new process, it launches a new tracker if it needs to create a new Semaphore

I see.  Is it an optimization problem, or does it risk leaking semaphores?  The problem is if a semaphore shared with the child isn't garbage collected correctly.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31310>
_______________________________________