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 tkessler
Recipients ned.deily, ronaldoussoren, tkessler
Date 2015-07-06.02:17:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436149068.06.0.463306574037.issue24573@psf.upfronthosting.co.za>
In-reply-to
Content
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 module. When the frame's mainloops are called the process crashes. I've included the script where this problem is occurring.

The crash report specifies python, and among a bunch of boilerplate information includes the following lines:

Application Specific Information:
*** multi-threaded process forked ***
crashed on child side of fork pre-exec

This is happening in Python 3.4.3, running in OS X 10.10.4. In testing this on alternative platforms (Windows and Linux) it appears to work, suggesting it may be a bug in OS X's implementation.
History
Date User Action Args
2015-07-06 02:17:48tkesslersetrecipients: + tkessler, ronaldoussoren, ned.deily
2015-07-06 02:17:48tkesslersetmessageid: <1436149068.06.0.463306574037.issue24573@psf.upfronthosting.co.za>
2015-07-06 02:17:47tkesslerlinkissue24573 messages
2015-07-06 02:17:47tkesslercreate