`test_import.test_concurrency` leaks ref on Windows

[sunmy2019]

On Python 3.12, test_import.test_concurrency() leaks on Windows:

vstinner@WIN C:\victor\python\3.12>python -m test test_import -m test_concurrency -R 3:3
(...)
test_import leaked [22, 36, 28] references, sum=86

bisected to #94504

Potentially Related: #104702

See #102251 (comment) #104796 (comment)

Linked PRs

• gh-106176: Fix reference leak in importlib/_bootstrap.py #106207
• GH-106176, GH-104702: Fix reference leak when importing across multiple threads #108497
• [3.12] GH-106176, GH-104702: Fix reference leak when importing across multiple threads (GH-108497) #108612

[vstinner]

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]

cc @exarkun @brettcannon

[Eclips4]

On Python 3.12, test_import.test_concurrency() leaks on Windows:

Did you mean that this test leaks only on 3.12?
I can still reproduce it on current main branch (3.13).

More info

./python -m test test_import -m test_concurrency -R 3:3
Running debug|x64 interpreter...
0:00:00 Run tests sequentially
0:00:00 [1/1] test_import
beginning 6 repetitions
123456
......
test_import leaked [40, 40, 40] references, sum=120
test_import leaked [40, 40, 40] memory blocks, sum=120
test_import failed (reference leak)

== Tests result: FAILURE ==

1 test failed:
    test_import

Total duration: 7.0 sec
Tests result: FAILURE

[sunmy2019]

Did you mean that this test leaks only on 3.12?

No. It also affects 3.12

[exarkun]

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.

[brettcannon]

@exarkun it just means some things are not getting cleaned up.

[exarkun]

Just trying to signal my likelihood of pitching on here: low.