[issue39074] Threading memory leak in _shutdown_locks for non-daemon threads

2020-01-06 Thread STINNER Victor
STINNER Victor added the comment: Ok, I close this issue as a duplicate of bpo-37788. -- nosy: +vstinner resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> fix for bpo-36402 (threading._shutdown() race condition) causes reference leak

[issue39074] Threading memory leak in _shutdown_locks for non-daemon threads

2019-12-17 Thread Adam
Adam added the comment: Looks like this issue might be a duplicate of https://bugs.python.org/issue37788 -- ___ Python tracker ___

[issue39074] Threading memory leak in _shutdown_locks for non-daemon threads

2019-12-17 Thread Adam
Change by Adam : -- type: resource usage -> security ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39074] Threading memory leak in _shutdown_locks for non-daemon threads

2019-12-17 Thread Adam
New submission from Adam : When running 3.7, we noticed a memory leak in threading._shutdown_locks when non-deamon threads are started but "join()" or "is_alive()" is never called. Here's a test to illustrate the growth: = import threading import time import tracemalloc def