Uh oh!
There was an error while loading. Please reload this page.
bpo-1635741: Fix reference cycle by calling explicit gc collection in main interpreter - #21902
Conversation
shihai1991
commented
Aug 17, 2020
Before this PR: After this PR: |
vstinner
commented
Aug 17, 2020
Merged since it seems to fix multiple issues: #21902 (comment) Does it fix your issue with encoding names and encodings._aliases? |
vstinner
commented
Aug 17, 2020
cc @ncoghlan@ericsnowcurrently: Python finalization is getting better ;-) Yet another GC collection at exit! |
shihai1991
commented
Aug 17, 2020
Yes, this PR have fix my issue. there have no remaining encodings.aliases in refdumps. |
vstinner
commented
Aug 18, 2020
I'm not sure that the GC is still fully functionnal after PyInterpreterState is cleared, but at least, it seems like there were a bunch of reference cycles. cc @pablogsal |
…honGH-21902) Fix a reference cycle by triggering an explicit GC collection after calling PyInterpreterState_Clear().
ghost
commented
Aug 26, 2020
Just curious, what are the three leaks. |
shihai1991
commented
Aug 26, 2020
You found this detail. I checked that some |
…honGH-21902) Fix a reference cycle by triggering an explicit GC collection after calling PyInterpreterState_Clear().
Authored-by: Victor Stinner vstinner@python.org
https://bugs.python.org/issue1635741