STINNER Victor added the comment:
It sounds like the reporter didn't use Valgrind properly. See last comments. If
Valgrind still reports issues when it's used properly, please reopen the issue
(or open a new issue). I close the issue for now.
--
resolution: -> not a bug
stage: ->
Charalampos Stratakis added the comment:
Another thing also, is to be sure to utilize the python's suppression file by
adding the --suppressions= to valgrind's command line invocation.
--
nosy: +cstratak
___
Python tracker
STINNER Victor added the comment:
By default, Python is optimized for performance but its pymalloc memory
allocator causes false alarms in Valgrind.
> https://github.com/python/cpython/blob/master/Misc/README.valgrind
This or you can disable pymalloc at runtime using:
PYTHONMALLOC=malloc
Tim Peters added the comment:
You're probably chasing ghosts ;-) Please read about what needs to be done to
use valgrind successfully with Python:
https://github.com/python/cpython/blob/master/Misc/README.valgrind
--
nosy: +tim.peters
title: Use After Free: PyObject_Free -> Use
