Evan Jones added the comment:
This is another instance of the following bug: http://bugs.python.org/issue27126
libdispatch (grand central dispatch) is not fork safe. The forkserver approach
is a good workaround, thanks!
--
nosy: +evan.jo...@bluecore.com
R. David Murray added the comment:
Your test code works for me on linux and python3.3 and 3.4.1. That is, I can
click four buttons and get back the prompt, with no segfault. It is quite
possible this is a bug in the Mac version of TK, assuming this is even supposed
to work.
--
Ronald Oussoren added the comment:
This is likely a known issue with using os.fork on OSX: that is unsafe, and
likely causes crashes, once one of Apple's frameworks has initialized.
I think it might be better in the long run to make multiprocessing on OSX
behave the same as on windows, but
Ned Deily added the comment:
A web search will find multiple hits for problems with using Tk (and Tkinter)
with multiprocess on OS X and elsewhere. On OS X, there is a well-known and
documented restriction that impacts Tk-based apps:
When launching separate processes using the fork function,
Topher Kessler added the comment:
Yeah it is a bug in OS X, fixed by setting the python multiprocessing start
method to 'forkserver' instead of the default fork.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24573
New submission from Topher Kessler:
There may be a bug in how tkinter frames are handled when called in multiple
processes in OS X.
I am trying to run a simple script that defines a new Frame subclass and then
attempts to call it multiple times in separate processes using the
multiprocessing
