Public issue detail

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

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

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

Last seen: 2026-06-05 03:12 UTC. Public JSON: /v1/issues/019e9114-5b91-76f3-b9b4-c11d578198d2

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/supervisord -n -c /etc/supervisor/supervisord.conf
  • 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 1 thread(s) around 0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: poll -> wait4 -> poll
  • Top syscalls: poll x5, wait4 x5, restart_syscall x1
  • Package: python3.13-minimal 3.13.12-1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f1c6e7efe92 in pthread_attr_destroy () from target:<path>
0x0000000000dd18b3 in ?? ()
0x00000000212ac01e in ?? ()
0x0000000000a56c88 in _PyRuntime ()
0x00007f1c6e7efead in ?? () from target:<path>
0x0000000000000007 in ?? ()
0x000000000054aeb0 in PyMem_Realloc ()
0x000000000067ca5b in ?? ()

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 python3.13: busy poll at unresolved offset in apt_pkg.cpython-313-x86_64-linux-gnu.so

possible duplicate

python3.13 is stuck in a likely busy poll loop: 8.66% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 2 thread(s) around 0x00007fe58a09affe in ?? () from target:<path> and 1 thread(s) around 0x00007fe587602f47 in pkgCache::PkgIterator::operator++() () from target:<path>.

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

Why this looks related: same classification, same package, same source package, same subsystem, same target

Last seen: 2026-06-10 02:24 UTC. Public page: /issues/019dd98b-0e1d-76e3-9171-f0f72c689536. Public JSON: /v1/issues/019dd98b-0e1d-76e3-9171-f0f72c689536

Runaway CPU investigation for ollama: busy poll at dequeue_entity

possible duplicate

ollama is stuck in a likely busy poll loop: 33.33% of sampled CPU passed through dequeue_entity, with repeated thread backtraces show 2 thread(s) around 0x00007f8964d81ffe in ?? () from target:<path> and 1 thread(s) around 0x0000564186607143 in ?? ().

highscore: 106reports: 1similarity: 85%

Why this looks related: same classification, same subsystem

Last seen: 2026-06-07 22:00 UTC. Public page: /issues/019db4dd-c68c-72b1-b12f-90ce87f6c4ba. Public JSON: /v1/issues/019db4dd-c68c-72b1-b12f-90ce87f6c4ba

Runaway CPU investigation for perl: busy poll at rb_erase

possible duplicate

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

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

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

Last seen: 2026-06-04 21:19 UTC. Public page: /issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321. Public JSON: /v1/issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321

Runaway CPU investigation for perl: busy poll at Perl_mg_find

possible duplicate

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

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

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

Last seen: 2026-06-03 21:35 UTC. Public page: /issues/019e7092-7bda-7273-8ce3-7e732bc3782d. Public JSON: /v1/issues/019e7092-7bda-7273-8ce3-7e732bc3782d

Runaway CPU investigation for perl: busy poll at __hrtimer_setup

possible duplicate

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

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

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

Last seen: 2026-06-05 21:37 UTC. Public page: /issues/019e9492-ba96-7f00-9599-ad575e4de4ca. Public JSON: /v1/issues/019e9492-ba96-7f00-9599-ad575e4de4ca

Runaway CPU investigation for rsync: busy poll at clear_page_erms

possible duplicate

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

highpackage: rsyncsource: rsyncscore: 106reports: 2similarity: 73%

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

Last seen: 2026-06-10 02:24 UTC. Public page: /issues/019e1a88-12a2-79f0-8a00-0794e663896a. Public JSON: /v1/issues/019e1a88-12a2-79f0-8a00-0794e663896a

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.