gh-129701: Fix a data race in intern_common in the free threaded build#130089
Uh oh!
There was an error while loading. Please reload this page.
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.
Use a mutex to avoid potentially returning a non-immortalized string, because immortalization happens after the insertion into the interned dict.
Use
Py_DECREF()calls instead ofPy_SET_REFCNT(s, Py_REFCNT(s) - 2)for thread-safety. This code path isn't performance sensitive, so just usePy_DECREF()unconditionally for simplicity.intern_commonwhen interning str objects in the free threading build #129701