This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients davin, pitrou, tomMoral
Date 2018-01-13.17:41:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1515865294.55.0.467229070634.issue31310@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2018-01-13 17:41:34pitrousetrecipients: + pitrou, davin, tomMoral
2018-01-13 17:41:34pitrousetmessageid: <1515865294.55.0.467229070634.issue31310@psf.upfronthosting.co.za>
2018-01-13 17:41:34pitroulinkissue31310 messages
2018-01-13 17:41:34pitroucreate