Public issue detail

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

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

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

Technical snapshot

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

Representative thread backtrace

  • Command: /usr/bin/xsltproc --path .:/woodpecker/src/gitea.osgeo.org/postgis/postgis/build-docs/../doc --param section.autolabel 1 --param section.label.includes.component.label 1 --param chunk.section.depth 0 --param generate.section.toc.level 2 --param toc.section.depth 1 --param funcsynopsis.style kr --param admon.graphics 1 --param admon.textlabel 0 --param make.clean.html 1 --param simplesect.in.toc 0 --param use.id.as.filename 1 --param chunk.quietly 1 --param header.rule 0 --param footer.rule 0 --param table.borders.with.css 1 --stringparam docbook.css.source --stringparam html.ext .html --stringparam saxon.character.representation decimal --nonet --stringparam html.stylesheet style.css?v=3803318182 --stringparam html.script postgis-ref-index.js?v=3803318182 example-blocks.js?v=3803318182 --stringparam postgis.visual.manifest /woodpecker/src/gitea.osgeo.org/postgis/postgis/build-docs/doc/html/images/visual-examples/manifest.xml --stringparam postgis.visual.version 3803318182 --output /woodpecker/src/gitea.osgeo.org/postgis/postgis/build-docs/doc/html/postgis-pl.html ./postgis-html.xsl postgis-out.xml
  • 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 0x00007fc89030a730 in xsltFindDocument () from target:<path>
  • 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: newfstatat -> newfstatat -> newfstatat
  • Top syscalls: newfstatat x97, brk x6
  • Package: xsltproc 1.1.45-0.1
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x00007fc89030a730 in xsltFindDocument () from target:<path>
0x00007fc890306ed9 in xsltKeyFunction () from target:<path>
0x00007fc890306cc7 in xsltKeyFunction () from target:<path>
0x00007fc8901cc691 in xmlXPathEvaluatePredicateResult () from target:<path>
0x00007fc8901cc4e8 in xmlXPathEvaluatePredicateResult () from target:<path>
0x00007fc8901cc3e4 in xmlXPathEvaluatePredicateResult () from target:<path>
0x00007fc8901cc49a in xmlXPathEvaluatePredicateResult () from target:<path>
0x00007fc8901cc38b in xmlXPathEvaluatePredicateResult () 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.

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

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

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

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

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.