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 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. ---------- components: Macintosh, Tkinter files: tkmultiproc.py messages: 246344 nosy: ned.deily, ronaldoussoren, tkessler priority: normal severity: normal status: open title: Using multiprocessing with tkinter frames in Python 3.4.3 crashes in OS X type: crash versions: Python 3.4 Added file: http://bugs.python.org/file39874/tkmultiproc.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24573> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com