[issue33526] hashlib leak on import

Alexander Mohr added the comment: closing as I'm not quite sure this is right -- stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue33526] hashlib leak on import

Christian Heimes added the comment: Thanks for notifying us. There isn't much we can do here. Python doesn't support unloading of C extension modules. The state will persist until the process ends. It doesn't make much sense to call EVP_cleanup() on shutdown, too. It will just slow down shutd

[issue33526] hashlib leak on import

Change by Christian Heimes : -- nosy: +petr.viktorin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue33526] hashlib leak on import

Change by Antoine Pitrou : -- nosy: +christian.heimes, gregory.p.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue33526] hashlib leak on import

New submission from Alexander Mohr : I'm seeing a lot of leaks via valgrind against the hashlib module. It appears that it's calling OpenSSL_add_all_digests(); on init, and never calling the corresponding EVP_Cleanup on free: https://www.openssl.org/docs/man1.1.0/crypto/OpenSSL_add_all_digest