New submission from STINNER Victor <vstin...@redhat.com>:
$ ./configure -C --enable-unicode=ucs4 --with-valgrind $ make $ valgrind --suppressions=Misc/valgrind-python.supp ./python -m test.regrtest test___all__ (...) ==18497== LEAK SUMMARY: ==18497== definitely lost: 324 bytes in 2 blocks ==18497== indirectly lost: 0 bytes in 0 blocks ==18497== possibly lost: 5,665,418 bytes in 27,453 blocks ==18497== still reachable: 8,530,840 bytes in 57,856 blocks ==18497== suppressed: 32 bytes in 1 blocks ==18497== Reachable blocks (those to which a pointer was found) are not shown. ==18497== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==18497== ==18497== For lists of detected and suppressed errors, rerun with: -s ==18497== ERROR SUMMARY: 4082 errors from 4082 contexts (suppressed: 0 from 0) I'm concerned by "324 bytes in 2 blocks". Attached PR fix it. Downstream issue: https://bugzilla.redhat.com/show_bug.cgi?id=1696322 Fixing "definitely lost" false alarm should help to catch real memory leaks. ---------- components: Extension Modules messages: 345985 nosy: vstinner priority: normal severity: normal status: open title: [2.7] valgrind python2 -m test.regrtest test___all__: definitely lost: 324 bytes in 2 blocks type: resource usage versions: Python 2.7 _______________________________________ 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
