STINNER Victor <vstin...@redhat.com> added the comment:
I confirm that my fix works with this manual test. I get "definitely lost: 0 bytes in 0 blocks" as expected: $ valgrind --suppressions=Misc/valgrind-python.supp ./python -m test.regrtest test___all__ (...) ==23782== LEAK SUMMARY: ==23782== definitely lost: 0 bytes in 0 blocks ==23782== indirectly lost: 0 bytes in 0 blocks ==23782== possibly lost: 17,945,740 bytes in 85,380 blocks ==23782== still reachable: 283,821 bytes in 475 blocks ==23782== suppressed: 2,605 bytes in 20 blocks ==23782== Reachable blocks (those to which a pointer was found) are not shown. ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37329> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
