STINNER Victor added the comment: Python 3.6 got a new PYTHONMALLOC env var which should help you ;-)
Please try to get the Python traceback on the crash and use Python builtin memory debugger: PYTHONMALLOC=debug python3 -X faulthandler ... > i've restarted this under valgrind to debug it. valgrind's startup of python > 3.6 is depressingly filled with invalid read of size n, (...) Python memory allocator pymalloc causes false alarms. You can disable pymalloc to use Valgrind using: PYTHONMALLOC=malloc valgrind python3 ... ---------- nosy: +haypo _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29470> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
