`tracemalloc` aborts when run from threads in no-gil

Crash report

What happened?

It's possible to get two different aborts from failed assertions, only with PYTHON_GIL=0, using the code below:

from threading import Thread
import _tracemalloc

alive = [
    Thread(target=_tracemalloc.start, args=(
        (memoryview(bytearray(b"abc\xe9\xff")),))),
    Thread(target=_tracemalloc.start, args=()),
    Thread(target=_tracemalloc.get_traceback_limit, args=()),
    Thread(target=_tracemalloc.start, args=()),
    Thread(target=_tracemalloc.stop, args=()),
    Thread(target=_tracemalloc.reset_peak, args=()),
    Thread(target=_tracemalloc.get_tracemalloc_memory, args=())
]

for obj in alive:
    print('START', obj)
    try:
        obj.start()
    except Exception:
        pass

The errors are:

python: Python/tracemalloc.c:445: tracemalloc_remove_trace: Assertion `tracemalloc_config.tracing' failed.
Aborted

And:

python: Python/tracemalloc.c:469: tracemalloc_add_trace: Assertion `tracemalloc_config.tracing' failed.
Aborted

Found with fusil by @vstinner.

CPython versions tested on:

CPython main branch

Operating systems tested on:

Linux

Output from running 'python -VV' on the command line:

Python 3.14.0a1+ experimental free-threading build (heads/main:d467d9246c, Nov 1 2024, 09:05:56) [GCC 11.4.0]

Comienza reproduciendo el ejemplo proporcionado con hilos usando una compilación experimental de free-threading y PYTHON_GIL=0. Inspecciona Python/tracemalloc.c alrededor de tracemalloc_remove_trace y tracemalloc_add_trace, y verifica después que el ejemplo ya no se interrumpe cuando se utilizan operaciones de tracemalloc de forma concurrente.