Runaway CPU investigation for python3.13: futex lock contention at _PyEval_EvalFrameDefault
possible duplicatepython3.13 is stuck in a likely futex lock contention loop: 3.20% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated thread backtraces show 2 thread(s) around 0x00007fb2d03589ee in futex_fatal_error () from target:<path> and 1 thread(s) around 0x00007fb2d03589ee in futex_fatal_error () from target:<path>.
Why this looks related: same classification, same subsystem, same wait site
Last seen: 2026-10-30 23:35 UTC. Public page: /issues/01a18e1b-e88d-7622-b075-af7da145ec9a. Public JSON: /v1/issues/01a18e1b-e88d-7622-b075-af7da145ec9a