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

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

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

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

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

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,

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

Change by Eitan Adler : -- nosy: +eadler ___ Python tracker ___ ___ Python-bugs-list

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

Changes by Ned Deily : -- priority: low -> normal stage: -> needs patch versions: +Python 3.5, Python 3.6, Python 3.7 ___ Python tracker

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

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.

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

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 ->

[issue13829] exception error in _scproxy.so

Carol Willing added the comment: Closed as an out of date issue. -- nosy: +willingc resolution: -> out of date status: open -> closed ___ Python tracker

[issue13829] exception error in _scproxy.so

Ronald Oussoren added the comment: Sigh... The crash is a subprocess started with fork is not entirely unexpected, although I had hoped that the current version of _scproxy would be safe enough. A number of Apple frameworks detect that a process called fork after they initialized and then

[issue13829] exception error in _scproxy.so

Julian Scheid added the comment: FWIW, I've run into the same issue in a homegrown application with 2.6.8, 2.7.2 and 2.7.3 (these were the only versions I've tested). Looking around a little bit, I suspect this might be a bug in SCDynamicStoreCopyProxies that's only present on OS X 10.7 and

[issue13829] exception error in _scproxy.so

Ronald Oussoren added the comment: I've once again reviewed the _scproxy code and that code seems correct (although that doesn't say too much for subtle bugs because I wrote the initial version of the module). Dan: is it possible to tell moviegrabber to use another python installation (in

[issue13829] exception error in _scproxy.so

Ronald Oussoren added the comment: If it is the moviegrabber I linked to: that's a 100% python script using some other opensource libraries. It does use multiprocessing, and that might mean this is the same problem as issue9405. That issue should be fixed in the repository (for a long time,

[issue13829] exception error in _scproxy.so

Changes by Brett Cannon br...@python.org: -- nosy: -brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13829 ___ ___ Python-bugs-list

[issue13829] exception error in _scproxy.so

Ned Deily n...@acm.org added the comment: The problem was originally discussed in these threads: http://mail.python.org/pipermail/pythonmac-sig/2011-December/023428.html http://mail.python.org/pipermail/pythonmac-sig/2011-December/023430.html Because _scproxy is used to get information about

[issue13829] exception error

Dan kamp bitbuc...@roontoon.com added the comment: I have received this from the macpython listserv it that helps. Would really like to find this issue. From the traceback, it appears that there is a problem with Python's _scproxy module; that's an internal helper C module that provides an

[issue13829] exception error

Brett Cannon br...@python.org added the comment: Then I'm going to assume the bug lies with Moviegrabber doing something wrong and it isn't Python's direct fault. -- resolution: - invalid status: open - closed ___ Python tracker

[issue13829] exception error

Brett Cannon br...@python.org added the comment: Can you isolate the cause? There is way too much in that core dump to try to debug the problem. Without knowing what code in this Moviegrabber app caused the bug we can't do anything to debug the issue. -- nosy: +brett.cannon status:

[issue13829] exception error

Dan kamp bitbuc...@roontoon.com added the comment: On Jan 20, 2012, at 4:20 PM, Brett Cannon wrote: Can you isolate the cause? There is way too much in that core dump to try to debug the problem. Without knowing what code in this Moviegrabber app caused the bug we can't do anything to

[issue13829] exception error

New submission from Dan kamp roont...@gmail.com: Get this error when trying to run Moviegrabber on a mac running v2.7. Crash report below. Process: Python [2444] Path: /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/C ontents/MacOS/Python