[issue37677] Seg Fault on OSX when multiprocessing

Ronald Oussoren added the comment: I'm closing this issue because this crash is caused by a platform issue, and Python 3.8 has a workaround by using a different spawn method in multiprocessing. -- resolution: -> out of date stage: -> resolved status: open -> closed

[issue37677] Seg Fault on OSX when multiprocessing

Ronald Oussoren added the comment: Looking at the stack trace this is a similar issue as the "no_proxy" one, but in some sense worse because it happens when just calling a regular unix API (not an Apple framework API). The first few lines of the stack trace are for code in the "Network"

[issue37677] Seg Fault on OSX when multiprocessing

Timothy Stonis added the comment: Hi, I have the exact same issue and same stack trace from getaddrinfo (except Python 2.7). Same as original poster, it only happens every couple of weeks and I don't know how to reproduce. For me it's in an Odoo instance that spawns multiple workers with

[issue37677] Seg Fault on OSX when multiprocessing

alvis added the comment: Hi, sorry i am unable to provide a standalone script that cause this issue, as it happen once every few weeks. Is it similar to the no_proxy=* issue? -- ___ Python tracker

[issue37677] Seg Fault on OSX when multiprocessing

Karthikeyan Singaravelan added the comment: Thanks for the report. It would be helpful to have a standalone reproducer for this issue to try reproducing it in 3.6 and other versions. -- nosy: +davin, pitrou, xtreak ___ Python tracker

[issue37677] Seg Fault on OSX when multiprocessing

New submission from alvis : Encountered a crash with the following logs. I have already added no_proxy=*, and it fixed the issue which i can replicate consistent. However, this crash does not happen every time, maybe once in a few week. Process: Python [66435] Path: