➜

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 vstinner
Recipients David Ford (FirefighterBlu3), christian.heimes, vstinner
Date 2017-02-07.09:47:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1486460835.11.0.457732217883.issue29470@psf.upfronthosting.co.za>
In-reply-to
Content 
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 ...
History
Date User Action Args
2017-02-07 09:47:15vstinnersetrecipients: + vstinner, christian.heimes, David Ford (FirefighterBlu3)
2017-02-07 09:47:15vstinnersetmessageid: <1486460835.11.0.457732217883.issue29470@psf.upfronthosting.co.za>
2017-02-07 09:47:15vstinnerlinkissue29470 messages
2017-02-07 09:47:14vstinnercreate