[issue13829] exception error in _scproxy.so when called after fork

[Ronald Oussoren]

Ronald Oussoren  added the comment:

I propose closing this as 3th-party or out-of-date:

1) The crash in _scproxy is due to limitations in Apple's libraries, in 
particular they don't work in child processes created with os.fork() without 
calling execv*()

2) The primary way to run into this is by the use of the multiprocessing 
library. The default spawn strategy for multiprocessing was changes to "spawn" 
instead of "fork" in 3.8 (for macOS) because of problems like this.

--
resolution:  -> out of date
stage: needs patch -> resolved
status: open -> pending

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[ThePokestarFan]

ThePokestarFan  added the comment:

Still present in python 3.8 and issue 38658. Another workaround is in 
https://bugs.python.org/issue30385#msg293958

--
nosy: +ThePokestarFan
versions: +Python 3.8

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[triccare triccare]

triccare triccare  added the comment:

I have run into this bug which can be reliably reproduced by importing tkinter.

However, I have found another workaround if one does not want to deal with the 
environmental variable and may point to a possible bug fix. Before forking, any 
use of `urlopen` alleviates the bug. This is demonstrated in the attached 
example.

Example works under Python 3.6.4 and Mac OS 10.12.6

--
nosy: +triccare triccare
Added file: https://bugs.python.org/file47503/debug_urlopen.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[Eitan Adler]

Change by Eitan Adler :


--
nosy: +eadler

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[Ned Deily]

Changes by Ned Deily :


--
priority: low -> normal
stage:  -> needs patch
versions: +Python 3.5, Python 3.6, Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[Evan Jones]

Evan Jones added the comment:

This is effectively the same as issue 27126. The discussion there convinced me 
that this may not be working around, since it isn't the only place this can 
happen! This same crash, caused by libdispatch not being fork compatible, also 
happens with sqlite and tk. We can probably add a workaround specifically for 
_scproxy.so, but those others would still cause the crash.

--
nosy: +evanj

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue13829] exception error in _scproxy.so when called after fork

[R. David Murray]

R. David Murray added the comment:

Why is it out of date?  Has it been fixed?  Has apple changed their abort 
policy?

Obviously it isn't high priority, though :)

--
assignee: ronaldoussoren -> 
nosy: +r.david.murray
priority: normal -> low
resolution: out of date -> 
status: closed -> open
title: exception error in _scproxy.so -> exception error in _scproxy.so when 
called after fork

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com