[Free-threading] `assert(!_Py_IsImmortal(op))` failure when BRC merge queue races with `sys.intern`
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- Python
- Estrelas
- 77.2k
- Forks
- 35.9k
- Métricas de merge de PRs
- Métricas de PR pendentes
Descrição
Bug report
Bug description:
In the free-threaded build, there is a race condition where an object can be queued for Biased Reference Counting (BRC) merging, but become immortal before the queue is processed. This causes a fatal C-level assertion failure:
assert.h assertion failed at Objects/object.c:467 in Py_ssize_t _Py_ExplicitMergeRefcount(PyObject *, Py_ssize_t): !_Py_IsImmortal(op)
*** Check failure stack trace: ***
@ _Py_ExplicitMergeRefcount
@ merge_queued_objects
@ _Py_brc_merge_refcounts
@ _Py_HandlePending
@ _PyEval_EvalFrameDefault
Reproduction. Fails when running under ASAN/TSAN and the free-threading build:
import threading
import sys
def test_race():
# 1 million strings will trap Thread A inside map() for milliseconds,
# giving Thread B plenty of time to queue references to strings that
# Thread A hasn't interned yet.
strings = ["race_string_massive_" + str(j) for j in range(1000000)]
# Give Thread B a copy of the list.
shared = list(strings)
def thread_b_func():
# Thread B clears its list, reducing the shared refcount to 0.
# Since Thread B is not the owner, they are placed in Thread A's merge queue.
shared.clear()
tb = threading.Thread(target=thread_b_func)
tb.start()
# Thread A executes entirely in C for milliseconds.
# Strings are queued by Thread B, AND THEN made immortal by sys.intern!
list(map(sys.intern, strings))
tb.join()
if __name__ == "__main__":
test_race()
CPython versions tested on:
3.14
Operating systems tested on:
Linux
Linked PRs
- gh-152277
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece por Objects/object.c em _Py_ExplicitMergeRefcount e rastreie o caminho de chamadas mencionado de merge_queued_objects, _Py_brc_merge_refcounts e _Py_HandlePending. Reproduza a condição de corrida com ASAN ou TSAN usando o build free-threaded e, em seguida, compare o comportamento e a resolução no PR vinculado gh-152277.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- c, python
- Domínio
- backend
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 30/100