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 ned.deily
Recipients Craig.Silverstein, ned.deily
Date 2014-01-23.01:19:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390439981.86.0.547315157487.issue20353@psf.upfronthosting.co.za>
In-reply-to
Content
I can reproduce a hang (but not a crash) when using a Python 2.7.x or 3.4.x built from source and linking with the OS X 10.9 system libsqlite3.  Using the Apple-supplied Python 2.7 on 10.9 causes a crash in libdispatch.  Using Python 2.7.6 or 3.4.0 from the current python.org 64-bit installers, the test does not hang; these Pythons are linked with a static local version of libsqlite3, not the system-supplied one.  If I modify the test to include a call to sqlite3.connect() in the top-level code before calling multiprocessing apply_async, the test also does not hang anymore. Perhaps you can use that as a workaround.  I'm not sure why the combination of sqlite and _tkinter are necessary to hang.  I'm not going to have time to look further into this right away.
History
Date User Action Args
2014-01-23 01:19:42ned.deilysetrecipients: + ned.deily, Craig.Silverstein
2014-01-23 01:19:41ned.deilysetmessageid: <1390439981.86.0.547315157487.issue20353@psf.upfronthosting.co.za>
2014-01-23 01:19:41ned.deilylinkissue20353 messages
2014-01-23 01:19:38ned.deilycreate