[issue27126] Mac system sqlite3 not fork safe: Bundle a version?

Changes by Evan Jones : Added file: http://bugs.python.org/file43004/osx_python3_crash.py ___ Python tracker <http://bugs.python.org/issue27126> ___ ___ Python-bugs-list m

[issue27126] Mac system sqlite3 not fork safe: Bundle a version?

New submission from Evan Jones: The system version of libsqlite3 that is included in Mac OS X is not fork safe. This means that if a process forks, and the child calls into it, it will crash with the stack trace below. I've reproduced this with both Python 2.7.10 and Python 3.5.1 on Mac

[issue24573] Using multiprocessing with tkinter frames in Python 3.4.3 crashes in OS X

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

[issue27126] Apple-supplied libsqlite3 on OS X is not fork safe; can cause crashes

Evan Jones added the comment: To be clear: My reproduction scripts crash both Python 2.7.10 and Python 3.5.1 when you: 1. Download the source bundle from python.org. 2. Run ./configure; make 3. Use the built binary (because ./configure picks up the system version of libsqlite.dylib) I did

[issue24085] large memory overhead when pyc is recompiled

New submission from Buck Evan: In the attached example I show that there's a significant memory overhead present whenever a pre-compiled pyc is not present. This only occurs with more than 5225 objects (dictionaries in this case) allocated. At 13756 objects, the mysterious pyc overhead

[issue24085] large memory overhead when pyc is recompiled

Buck Evan added the comment: Also, we've reproduced this in both linux and osx. -- ___ Python tracker <http://bugs.python.org/issue24085> ___ ___ Pytho

[issue24085] large memory overhead when pyc is recompiled

Buck Evan added the comment: New data: The memory consumption seems to be in the compiler rather than the marshaller: ``` $ PYTHONDONTWRITEBYTECODE=1 python -c 'import repro' 16032 $ PYTHONDONTWRITEBYTECODE=1 python -c 'import repro' 16032 $ PYTHONDONTWRITEBYTECODE=1 pyt

[issue24085] large memory overhead when pyc is recompiled

Buck Evan added the comment: @serhiy.storchaka This is a very stable piece of a legacy code base, so we're not keen to refactor it so dramatically, although we could. We've worked around this issue by compiling pyc files ahead of time and taking extra care that they're pr

<    1   2