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 gregory.p.smith
Recipients Adq, gregory.p.smith, terry.reedy, vinay.sajip
Date 2020-10-22.03:59:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603339157.68.0.43136475228.issue42097@roundup.psfhosted.org>
In-reply-to
Content
If you use os.fork() or any of the multiprocessing start methods that call os.fork() with a process involving threads, this is expected behavior.  os.fork() cannot be used in processes that have threads without potential for deadlock.

Specifically, make sure you explicitly call:

 multiprocessing.set_start_method('spawn')

before using multiprocessing in any application where threads exist.

It is possible to use 'forkserver' as well, but only if you ensure the multiprocessing forkserver process is started before your application has launched any threads.
History
Date User Action Args
2020-10-22 03:59:17gregory.p.smithsetrecipients: + gregory.p.smith, terry.reedy, vinay.sajip, Adq
2020-10-22 03:59:17gregory.p.smithsetmessageid: <1603339157.68.0.43136475228.issue42097@roundup.psfhosted.org>
2020-10-22 03:59:17gregory.p.smithlinkissue42097 messages
2020-10-22 03:59:17gregory.p.smithcreate