bpo-37788: Fix reference leak when Thread is never joined#27473
bpo-37788: Fix reference leak when Thread is never joined#27473millerjoey975 wants to merge 0 commit intopython:mainpython/cpython:mainfrom millerjoey975:buildbot-custommillerjoey975/cpython:buildbot-customCopy head branch name to clipboard
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). Recognized GitHub usernameWe couldn't find a bugs.python.org (b.p.o) account corresponding to the following GitHub usernames: This might be simply due to a missing "GitHub Name" entry in one's b.p.o account settings. This is necessary for legal reasons before we can look at this contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
|
Sorry. I don't understand why to create this PR again? This patch have been merged in: #26103. |
|
Indeed, this is a null PR. @millerjoey975, please explain. |
When a Thread is not joined after it has stopped, its lock may remain in the _shutdown_locks
set until interpreter shutdown. If many threads are created this way, the _shutdown_locks
set could therefore grow endlessly. To avoid such a situation, purge expired locks each
time a new one is added or removed.
https://bugs.python.org/issue37788