You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test_import.test_concurrency leaks ref on Windows #106176
We could revert the fix that leads to the leak to unblock the release as I'm not sure if anyone has come up with a good solution to avoid the memory leak and the bugs that get fixed are not fundamental to import (although it would still be nice to have the bugs fixed).
Activity
vstinner commentedon Jun 28, 2023
This leak can be seen on the "AMD64 Windows11 Refleaks 3.12" buildbot for example: https://buildbot.python.org/all/#/builders/1103/builds/36
I reproduced it locally.
vstinner commentedon Jun 28, 2023
cc @exarkun @brettcannon
Eclips4 commentedon Jun 28, 2023
Did you mean that this test leaks only on 3.12?
I can still reproduce it on current main branch (3.13).
More info
sunmy2019 commentedon Jun 28, 2023
No. It also affects 3.12
exarkun commentedon Jun 28, 2023
I'm not familiar with the leak checking system and I'm not likely to have much time to learn about it in the foreseeable future.
pythongh-106176: Fix reference leak in importlib/_bootstrap.py
brettcannon commentedon Jun 28, 2023
@exarkun it just means some things are not getting cleaned up.
exarkun commentedon Jun 29, 2023
Just trying to signal my likelihood of pitching on here: low.
vstinner commentedon Jul 23, 2023
Oops, I just reported a duplicate of this bug: #107086 (closed).
I also found the same commit with git bisect: commit 3325f05
vstinner commentedon Jul 23, 2023
A fix was proposed: PR #106207.
erlend-aasland commentedon Aug 1, 2023
@Yhg1s: IMO, this is also a release blocker (in my opinion, any ref leak is a release blocker).
Yhg1s commentedon Aug 1, 2023
(Yes, this looks like a real leak, not an artifact of how the refleak checker reruns things, so it should be a release blocker.)
brettcannon commentedon Aug 2, 2023
We could revert the fix that leads to the leak to unblock the release as I'm not sure if anyone has come up with a good solution to avoid the memory leak and the bugs that get fixed are not fundamental to import (although it would still be nice to have the bugs fixed).
pythonGH-106176: Fix reference leak when importing across multiple th…
brettcannon commentedon Aug 25, 2023
I created #108497 to try out an idea that @Eclips4 had for using weakrefs.
GH-106176, GH-104702: Fix reference leak when importing across multip…
pythonGH-106176, pythonGH-104702: Fix reference leak when importing a…
[3.12] GH-106176, GH-104702: Fix reference leak when importing across…