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 barry
Recipients barry, davin, kapilt, ned.deily, pitrou, ronaldoussoren
Date 2018-11-15.03:22:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542252155.76.0.788709270274.issue33725@psf.upfronthosting.co.za>
In-reply-to
Content
I have a reliable way to call *something* in the pthread_atfork prepare handler, but I honestly don't know what to call to prevent the crash.

In the Ruby thread, it seemed to say that you could just dlopen /System/Library/Frameworks/Foundation.framework/Foundation but that does not work for me.  Neither does also loading the CoreFoundation and SystemConfiguration frameworks.

If anybody has something that will reliably initialize the runtime, I can post my approach (there are a few subtleties).  Short of that, I think there's nothing that can be done except ensure that exec is called right after fork.
History
Date User Action Args
2018-11-15 03:22:35barrysetrecipients: + barry, ronaldoussoren, pitrou, ned.deily, davin, kapilt
2018-11-15 03:22:35barrysetmessageid: <1542252155.76.0.788709270274.issue33725@psf.upfronthosting.co.za>
2018-11-15 03:22:35barrylinkissue33725 messages
2018-11-15 03:22:35barrycreate