Public issue detail

Runaway CPU investigation for packagekitd: busy poll at unresolved offset in libglib-2.0.so.0.8800.0

packagekitd is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through 0x000000000005ad75, with repeated ppoll x4, <... ppoll resumed>) = 0 x1, futex x1.

highpackage: packagekitsource: packagekitscore: 106reports: 2

Last seen: 2026-03-29 18:31 UTC. Public JSON: /v1/issues/019d3a09-5db3-70e1-9882-25c4bc1d7196

Technical snapshot

This is the stack-shaped slice and hot path Fixer captured while the process was spinning.

Sampled wait stack

  • Command: /usr/libexec/packagekitd
  • Why Fixer classified it this way: The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.
  • Wait site: poll_schedule_timeout.constprop.0
  • Hot path: 0x000000000005ad75 (100.00% sampled CPU)
  • Repeated loop: futex -> ppoll -> ppoll
  • Top syscalls: ppoll x4, <... ppoll resumed>) = 0 x1, futex x1
  • Package: packagekit
poll_schedule_timeout.constprop.0
do_sys_poll
__x64_sys_ppoll
do_syscall_64
entry_SYSCALL_64_after_hwframe

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 postgres: busy poll at sqlite3VdbeExec

possible duplicate

postgres is stuck in a likely busy poll loop: 9.57% of sampled CPU passed through sqlite3VdbeExec, with repeated thread backtraces show 1 thread(s) around 0x00007f3dd70ac60d in select () from target:<path>.

highscore: 106reports: 1similarity: 62%

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

Last seen: 2026-10-02 18:03 UTC. Public page: /issues/019f9de5-ae93-70a0-b43c-cc5fcfe33721. Public JSON: /v1/issues/019f9de5-ae93-70a0-b43c-cc5fcfe33721

Runaway CPU investigation for perl: busy poll at perf_ctx_enable

possible duplicate

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through perf_ctx_enable, with repeated thread backtraces show 1 thread(s) around 0x00007f82eb9e87d2 in ?? () from target:<path>.

highpackage: perl-basesource: perlscore: 106reports: 2successful triagesimilarity: 60%

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

Last seen: 2026-10-24 03:30 UTC. Public page: /issues/019e4743-6f51-7fc1-b372-9900d37706a1. Public JSON: /v1/issues/019e4743-6f51-7fc1-b372-9900d37706a1

Runaway CPU investigation for python3.13: busy poll at read_tsc

possible duplicate

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through read_tsc, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagesimilarity: 58%

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

Last seen: 2026-10-10 01:56 UTC. Public page: /issues/019da8df-cd0c-7880-ab1e-6dd908d64437. Public JSON: /v1/issues/019da8df-cd0c-7880-ab1e-6dd908d64437

Runaway CPU investigation for python3.13: busy poll at idle_cpu

possible duplicate

python3.13 is stuck in a likely busy poll loop: 40.65% of sampled CPU passed through idle_cpu, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagesimilarity: 58%

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

Last seen: 2026-10-04 02:36 UTC. Public page: /issues/019dfead-0293-7062-b24e-c9b04c2f1edb. Public JSON: /v1/issues/019dfead-0293-7062-b24e-c9b04c2f1edb

Runaway CPU investigation for perl: busy poll at wakeup_preempt

possible duplicate

perl is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through wakeup_preempt, with repeated thread backtraces show 1 thread(s) around __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44.

highpackage: perl-basesource: perlscore: 106reports: 1similarity: 57%

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

Last seen: 2026-10-24 08:15 UTC. Public page: /issues/01a16cfa-9730-72e0-bcbd-c54d60d21608. Public JSON: /v1/issues/01a16cfa-9730-72e0-bcbd-c54d60d21608

Runaway CPU investigation for python3.13: busy poll at _PyEval_FrameClearAndPop

possible duplicate

python3.13 is stuck in a likely busy poll loop: 50.00% of sampled CPU passed through _PyEval_FrameClearAndPop, with repeated thread backtraces show 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2successful triagesimilarity: 55%

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

Last seen: 2026-10-25 16:09 UTC. Public page: /issues/019dd062-04a8-7e03-b3a3-5bb273aa2f42. Public JSON: /v1/issues/019dd062-04a8-7e03-b3a3-5bb273aa2f42

Worker outcome summary

This issue has 3 recorded worker attempts. 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.

3 failed patch attempts

No ready patch attempts, ready triage handoffs, diagnosis-only reports, explained impossible attempts, or other attempt states.

Most common blockers

  • patch proposal did not complete cleanly (3 attempts)

Published attempts

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 15:07 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 15:06 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

failed patch attempt

patch

packagekitd likely remains stuck in a busy poll loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 14:57 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

  • This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
  • Subsystem: runaway-process
  • Diagnosis family: busy-poll
  • Hot path: 0x000000000005ad75
  • Command: /usr/libexec/packagekitd
  • Source package: packagekit
  • Workspace source: debian-source
  • Workspace acquisition: Fetched Debian source package via apt-get source.
  • Homepage: https://www.freedesktop.org/software/PackageKit/
  • Implicated packages: libglib2.0-0t64

The trace repeatedly returns to a poll-family syscall without meaningful blocking, which suggests a busy event-loop wakeup.

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