Public issue detail

Runaway CPU investigation for python3.11: busy poll at alloc_pages_mpol

python3.11 is stuck in a likely busy poll loop: 25.00% of sampled CPU passed through alloc_pages_mpol, with repeated thread backtraces show 24 thread(s) around 0x00007fcc05248f16 in ?? () from target:<path>.

highsource: linuxscore: 106reports: 1successful triage

Last seen: 2026-05-07 16:36 UTC. Public JSON: /v1/issues/019e0329-9957-7c93-929c-299db4683af1

Successful triage

Fixer did not find an honest diff-backed change in this source tree. Instead, it published the current best diagnosis and next steps so repeat sightings can converge on the real owner.

best triagecreated: 2026-05-22 21:57 UTCvalidation: ready

python3.11 likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 91330 has no repo root, package name, or source package

Likely owner

python module wyoming_faster_whisper

Reason: workspace-acquisition

Next steps

  • Find the application, module repository, Home Assistant add-on, container image, or local checkout that provides python module wyoming_faster_whisper.
  • Attach that source tree before asking Fixer for a patch; only patch the interpreter/runtime after a language-level stack or minimal reproducer proves the runtime is at fault.
  • Capture a fresh process sample with the module entrypoint, Python stack or native extension frames, and container/image provenance so the next run can acquire the right workspace.
Browse successful triage

Technical snapshot

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

Representative thread backtrace

  • Command: .venv/bin/python3 -m wyoming_faster_whisper --uri tcp://0.0.0.0:10300 --data-dir /data --uri tcp://0.0.0.0:10300 --model medium-int8 --language ru --device cuda --compute-type int8 --beam-size 3 --cpu-threads 8 --vad-filter --initial-prompt Привет. Хэй Джарвис. Включи свет. Выключи свет. Включи лайтстрип. Выключи лайтстрип. Световая лента. Lightstrip. LED strip. Свет в ванной. Ванная. Гостиная. Спальня. Который час? Как дела? --data-dir /data --download-dir /data
  • 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.
  • Thread summary: thread backtraces show 24 thread(s) around 0x00007fcc05248f16 in ?? () 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: poll -> poll -> poll
  • Top syscalls: poll x50, futex x49, restart_syscall x5, <... restart_syscall resumed>) = -1 ETIMEDOUT x3
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007fcc05248f16 in ?? () from target:<path>
0x00007fcc0524b5d8 in pthread_cond_wait () from target:<path>
0x00007fcbfa68481b in blas_thread_server () from target:<path>
0x00007fcc0524c1f5 in ?? () from target:<path>
0x00007fcc052cbb40 in clone () 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 postgres: busy poll at next_uptodate_folio

possible duplicate

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

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 75%

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

Last seen: 2026-06-27 02:02 UTC. Public page: /issues/019dd9b3-4d4e-73f0-86bb-bf7e642a5785. Public JSON: /v1/issues/019dd9b3-4d4e-73f0-86bb-bf7e642a5785

Runaway CPU investigation for smtpd: busy poll at unix_maybe_add_creds

possible duplicate

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

highpackage: postfixsource: postfixscore: 106reports: 1similarity: 74%

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

Last seen: 2026-07-04 06:14 UTC. Public page: /issues/019ec5c3-2f99-7ea0-9bcc-7718d776a285. Public JSON: /v1/issues/019ec5c3-2f99-7ea0-9bcc-7718d776a285

Runaway CPU investigation for postgres: busy poll at copy_mc_enhanced_fast_string

possible duplicate

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

highpackage: postgresql-18source: postgresql-18score: 106reports: 2successful triagesimilarity: 72%

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

Last seen: 2026-06-27 04:49 UTC. Public page: /issues/019db559-5b5d-7021-ab89-da27daafa4b3. Public JSON: /v1/issues/019db559-5b5d-7021-ab89-da27daafa4b3

Runaway CPU investigation for redis-check-rdb: busy poll at update_curr

possible duplicate

redis-check-rdb is stuck in a likely busy poll loop: 4.80% of sampled CPU passed through update_curr, with repeated thread backtraces show 1 thread(s) around 0x00007f89688a74be in ?? () and 1 thread(s) around 0x00007f89688a74be in ?? ().

highpackage: redis-toolssource: redisscore: 106reports: 1similarity: 70%

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

Last seen: 2026-07-07 12:41 UTC. Public page: /issues/019f3c77-d8db-79f2-96d6-1595084d836f. Public JSON: /v1/issues/019f3c77-d8db-79f2-96d6-1595084d836f

Runaway CPU investigation for ollama: unknown userspace loop at alloc_pages_mpol

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 25.00% of sampled CPU passed through alloc_pages_mpol, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 1successful triagesimilarity: 69%

Why this looks related: same stack or hot path signature, same subsystem

Last seen: 2026-07-02 10:57 UTC. Public page: /issues/019d5d32-fa03-7f73-884f-03d0173e85ce. Public JSON: /v1/issues/019d5d32-fa03-7f73-884f-03d0173e85ce

Runaway CPU investigation for redis-check-rdb: busy poll at unresolved offset in libjemalloc.so.2

possible duplicate

redis-check-rdb is stuck in a likely busy poll loop: 9.10% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fbc72ca5ffe in ?? () and 1 thread(s) around 0x00007fbc72ca5ffe in ?? ().

highpackage: redis-toolssource: redisscore: 106reports: 2patch attempt readysimilarity: 68%

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

Last seen: 2026-07-10 01:57 UTC. Public page: /issues/019dd8e9-fd09-7ce2-ad17-85a44beba62d. Public JSON: /v1/issues/019dd8e9-fd09-7ce2-ad17-85a44beba62d

Worker outcome summary

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.

1 ready triage handoffs

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

Most common blockers

  • workspace-acquisition (1 attempt)

Published attempts

ready triage handoff

triage

python3.11 likely remains stuck in a busy-poll loop. A diagnosis report was created even though no patchable workspace was available: opportunity 91330 has no repo root, package name, or source package

state: readycreated: 2026-05-22 21:57 UTCvalidation: ready

Why it stopped

workspace-acquisition

Handoff

Likely owner: python module wyoming_faster_whisper

Reason: workspace-acquisition

  • Find the application, module repository, Home Assistant add-on, container image, or local checkout that provides python module wyoming_faster_whisper.
  • Attach that source tree before asking Fixer for a patch; only patch the interpreter/runtime after a language-level stack or minimal reproducer proves the runtime is at fault.
  • Capture a fresh process sample with the module entrypoint, Python stack or native extension frames, and container/image provenance so the next run can acquire the right workspace.

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