Public issue detail

Runaway CPU investigation for python3.14: file not found retry at void CppDeallocPtr<Configuration*>(_object*)

python3.14 is stuck in a likely file not found retry loop: 11.35% of sampled CPU passed through void CppDeallocPtr<Configuration*>(_object*), with repeated thread backtraces show 2 thread(s) around __syscall_cancel_arch () at ..<path>:56 and 1 thread(s) around __ctype_b_loc () at ..<path>:43.

highpackage: python3.14-minimalsource: python3.14score: 106reports: 1

Last seen: 2026-10-12 18:34 UTC. Public JSON: /v1/issues/019f6914-4c2c-7460-a165-72bb0ce46cbd

Technical snapshot

This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.

Representative thread backtrace

  • Command: /usr/bin/python3 /usr/bin/unattended-upgrade
  • Why Fixer classified it this way: The trace keeps retrying file lookups that fail with ENOENT, which suggests a missing-file retry loop.
  • Thread summary: thread backtraces show 2 thread(s) around __syscall_cancel_arch () at ..<path>:56 and 1 thread(s) around __ctype_b_loc () at ..<path>:43
  • Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: 43 ..<path>: No such file or directory
  • Repeated loop: newfstatat -> newfstatat -> newfstatat
  • Top syscalls: newfstatat x62634, read x63, lseek x57, fcntl x4
  • Package: python3.14-minimal 3.14.7-4
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
__syscall_cancel_arch () at ..<path>:56
0x00007fd4354d09d4 in __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:49
0x00007fd4354d0a1d in __syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:75
0x00007fd43554545e in __GI_ppoll (fds=..., nfds=..., timeout=..., sigmask=...) at ..<path>:42
0x00007fd432ea447e in g_get_monotonic_time_ns () from target:<path>
0x00007fd432ea4d20 in g_main_context_iteration () from target:<path>
0x00007fd432ea4d71 in g_main_context_iteration () from target:<path>
0x00007fd432ed9ea0 in g_private_set () from target:<path>

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

python3.14 is stuck in a likely busy poll loop: 13.66% of sampled CPU passed through void CppDeallocPtr<Configuration*>(_object*), with repeated thread backtraces show 2 thread(s) around __syscall_cancel_arch () at ..<path>:56 and 1 thread(s) around 0x00007fbe346fe8a4 in void CppDeallocPtr<Configuration*>(_object*) () from target:<path>.

highpackage: python3.14-minimalsource: python3.14score: 106reports: 1similarity: 99%

Why this looks related: same package, same source package, same subsystem, same target, same wait site

Last seen: 2026-10-22 20:04 UTC. Public page: /issues/019f786b-ccc8-7e90-8fee-186a079214f0. Public JSON: /v1/issues/019f786b-ccc8-7e90-8fee-186a079214f0

pdftex is stuck in a likely file not found retry loop: 16.24% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x0000559cf35425aa in ?? ().

highscore: 106reports: 1similarity: 66%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-10-02 09:54 UTC. Public page: /issues/019f76fe-e585-7490-a51d-2e41820f45d3. Public JSON: /v1/issues/019f76fe-e585-7490-a51d-2e41820f45d3

xsltproc is stuck in a likely file not found retry loop: 71.03% of sampled CPU passed through xsltFindDocument, with repeated thread backtraces show 1 thread(s) around 0x00007fc89030a730 in xsltFindDocument () from target:<path>.

highpackage: xsltprocsource: libxsltscore: 106reports: 1similarity: 63%

Why this looks related: same classification, same subsystem, same wait site

Last seen: 2026-10-21 04:56 UTC. Public page: /issues/019f76a7-76bc-7333-a696-3d38b95d7023. Public JSON: /v1/issues/019f76a7-76bc-7333-a696-3d38b95d7023

Published attempts

No public attempts have been published for this issue yet.