Public issue detail

Runaway CPU investigation for pdftex: file not found retry at unresolved offset in libz.so.1.3.1

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: 1

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

Technical snapshot

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

Representative thread backtrace

  • Command: pdflatex -interaction=batchmode postgis-out.tex
  • 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 1 thread(s) around 0x0000559cf35425aa in ?? ()
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container. warning: Expected absolute pathname for libpthread in the inferior, but got target:<path> warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
  • Repeated loop: access -> access -> access
  • Top syscalls: access x14534, openat x14280, getdents64 x740, newfstatat x574
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x0000559cf35425aa in ?? ()
0x0000559cf356850a in ?? ()
0x0000559cf356d3f5 in ?? ()
0x0000559cf351c83c in ?? ()
0x0000559cf3587ca5 in ?? ()
0x0000559cf3525590 in ?? ()
0x0000559cf3510312 in ?? ()
0x00007f5010475ca8 in getbroadcastnets () 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.

Runaway CPU investigation for xsltproc: file not found retry at xsltFindDocument

possible duplicate

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: 73%

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

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

possible duplicate

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: 1similarity: 66%

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

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

Runaway CPU investigation for po2xml: unknown userspace loop at unresolved offset in libpcre2-16.so.0.14.0

possible duplicate

po2xml is stuck in a likely unclassified userspace loop: 53.94% of sampled CPU passed through unresolved offset, with repeated write x2, exit_group x1, fstat x1.

highscore: 106reports: 1similarity: 53%

Why this looks related: same subsystem, same wait site

Last seen: 2026-10-19 03:46 UTC. Public page: /issues/01a0f656-df4b-7fc2-acb4-c03fc6235e66. Public JSON: /v1/issues/01a0f656-df4b-7fc2-acb4-c03fc6235e66

Runaway CPU investigation for lto1: unknown userspace loop at bitmap_set_bit(bitmap_head*, int)

possible duplicate

lto1 is stuck in a likely unclassified userspace loop: 2.51% of sampled CPU passed through bitmap_set_bit(bitmap_head*, int), with repeated thread backtraces show 1 thread(s) around 0x000000000162a9f7 in constrain_operands(int, unsigned long) ().

highscore: 106reports: 1similarity: 46%

Why this looks related: same subsystem, same wait site

Last seen: 2026-09-30 11:46 UTC. Public page: /issues/019fa772-cf3b-7890-82d2-60e7dba39362. Public JSON: /v1/issues/019fa772-cf3b-7890-82d2-60e7dba39362

Published attempts

No public attempts have been published for this issue yet.

Quarantine stays on by default so the public queue is harder to spam.