[3.13] gh-117657: Fix race involving GC and heap initialization (GH-119923) #120038
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
_PyThreadState_Bind()
function is called before the firstPyEval_AcquireThread()
so it's not synchronized with the stop theworld GC. We had a race where
gc_visit_heaps()
might visit a thread'sheap while it's being initialized.
Use a simple atomic int to avoid visiting heaps for threads that are not
yet fully initialized (i.e., before
tstate_mimalloc_bind()
is called).The race was reproducible by running:
python Lib/test/test_importlib/partial/pool_in_threads.py
.(cherry picked from commit e69d068)
Co-authored-by: Sam Gross colesbury@gmail.com