bpo-33895: Relase GIL while calling functions that acquire Windows loader lock #7789
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. When your account is ready, please add a comment in this pull request Thanks again for your contribution, we look forward to reviewing it! |
…ader lock Windows functions LoadLibrary, GetProcAddress, FreeLibrary and GetModuleHandle use the system loader lock. Calling these while holding the GIL will cause a dead lock in the rare occasion that another thread is detaching and needs to destroy its thread state at the same time.
tonyroberts
force-pushed
the
fix-issue-33895
branch
from
7c9a089
to
3255879
Compare
|
CLA has been signed, but only this morning so probably not processed yet. |
|
Retriggering the CI systems, as I believe this is ready to merge. |
Windows functions LoadLibrary, GetProcAddress, FreeLibrary and GetModuleHandle use the system loader lock. Calling these while holding the GIL will cause a dead lock in the rare occasion that another thread
is detaching and needs to destroy its thread state at the same time.
https://bugs.python.org/issue33895