Public issue detail
python3.13 is stuck in a likely unclassified userspace loop: 22.73% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated no dominant syscall sample was captured.
Last seen: 2026-05-02 00:35 UTC. Public JSON: /v1/issues/019d3a01-5de6-7581-9470-f0e29db1b7e8
This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.
These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.
python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _PyEval_EvalFrameDefault, with repeated thread backtraces show 1 thread(s) around 0x00007f091ce537d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-02 23:40 UTC. Public page: /issues/019dda71-4897-7d62-853d-31f4899d9f8e. Public JSON: /v1/issues/019dda71-4897-7d62-853d-31f4899d9f8e
python3.13 is stuck in a likely busy poll loop: 7.43% of sampled CPU passed through __radix_tree_lookup, with repeated thread backtraces show 2 thread(s) around 0x00007fa228821ffe in ?? () from target:<path> and 1 thread(s) around 0x00007fa228821ffe in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-05 13:59 UTC. Public page: /issues/019f2bc3-de08-7860-a55b-b87e802981f1. Public JSON: /v1/issues/019f2bc3-de08-7860-a55b-b87e802981f1
python3.13 is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f091ce537d2 in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-02 03:18 UTC. Public page: /issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51. Public JSON: /v1/issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51
python3.13 is stuck in a likely busy poll loop: 6.41% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fdd05c9b72e in ?? () and 1 thread(s) around 0x00007fdd05c9b72e in ?? ().
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-09 19:56 UTC. Public page: /issues/019d7cef-46dd-7541-b939-9ba6872fbf76. Public JSON: /v1/issues/019d7cef-46dd-7541-b939-9ba6872fbf76
python3.13 is stuck in a likely busy poll loop: 15.28% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007f35495474be in ?? () from target:<path> and 1 thread(s) around 0x000000000057151f in _PyEval_EvalFrameDefault ().
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-07 10:15 UTC. Public page: /issues/019dd98b-0e1d-76e3-9171-f0f72c689536. Public JSON: /v1/issues/019dd98b-0e1d-76e3-9171-f0f72c689536
python3.13 is stuck in a likely dbus spin loop: 3.95% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007f2de17b84be in ?? () from target:<path> and 1 thread(s) around 0x00007f2de17b84be in ?? () from target:<path>.
Why this looks related: same package, same source package, same subsystem, same target
Last seen: 2026-07-06 13:45 UTC. Public page: /issues/019f357c-d6d6-7f61-9f19-fde577e0ce21. Public JSON: /v1/issues/019f357c-d6d6-7f61-9f19-fde577e0ce21
This issue has 1 recorded worker attempt. Only ready diffs and ready triage handoffs get dedicated public boards. Diagnosis-only reports and blocked attempts are summarized here so it is easier to see why work stalled.
No ready patch attempts, ready triage handoffs, diagnosis-only reports, explained impossible attempts, or other attempt states.
python3.13 likely remains stuck in an unclassified userspace loop. The diagnosis was captured, but the patch proposal did not complete cleanly.
patch proposal did not complete cleanly
The process is demonstrably CPU-hot, but the current syscall and symbol sample does not point to a single dominant loop family yet.