Public issue detail

Runaway CPU investigation for perl: busy poll at __select

perl is stuck in a likely busy poll loop: 100.00% of sampled CPU passed through __select, 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: 1

Last seen: 2026-11-05 14:33 UTC. Public JSON: /v1/issues/01a1ac21-3fbf-7531-a194-e3073425fdb0

Technical snapshot

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

Representative thread backtrace

  • Command: /usr/bin/perl -wT /usr/sbin/munin-node --foreground
  • 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 __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: 44 .<path>: No such file or directory
  • Repeated loop: pselect6 -> pselect6 -> pselect6
  • Top syscalls: pselect6 x3
  • Package: perl-base 5.42.3-1
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
__internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:44
0x00007fdf94a22a1d in __syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:75
0x00007fdf94aa18af in __GI___select (nfds=..., readfds=..., writefds=..., exceptfds=..., timeout=...) at ..<path>:69
0x000056352b7c546c in Perl_sortsv ()
0x000056352b82afa6 in Perl_runops_standard ()
0x000056352b703f85 in perl_run ()
0x000056352b6d46ae in main ()

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.

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

Why this looks related: same classification, same package, same source package, same subsystem, same target, 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

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

Why this looks related: same classification, same package, same source package, same subsystem, same target, same wait site, very similar public summary

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

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

highpackage: postgresql-18source: postgresql-18score: 106reports: 1similarity: 73%

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

Last seen: 2026-11-05 14:14 UTC. Public page: /issues/019dc250-4c8b-7812-88a9-0d10a9b035ea. Public JSON: /v1/issues/019dc250-4c8b-7812-88a9-0d10a9b035ea

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

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

Last seen: 2026-11-05 17:49 UTC. Public page: /issues/019dd062-04a8-7e03-b3a3-5bb273aa2f42. Public JSON: /v1/issues/019dd062-04a8-7e03-b3a3-5bb273aa2f42

postgres is stuck in a likely socket churn loop: 1.38% of sampled CPU passed through ext4_match, with repeated thread backtraces show 1 thread(s) around 0x00007f70957eb687 in __GI__IO_flush_all () from target:<path>.

highsource: linuxscore: 106reports: 1similarity: 53%

Why this looks related: same subsystem, same wait site

Last seen: 2026-11-16 20:23 UTC. Public page: /issues/019f7768-5716-70d2-ad90-040b55fcd8f0. Public JSON: /v1/issues/019f7768-5716-70d2-ad90-040b55fcd8f0

sshd-session is stuck in a likely unclassified userspace loop: 100.00% of sampled CPU passed through sock_poll, with repeated thread backtraces show 1 thread(s) around 0x00007f35fa09a7d2 in ?? () from target:<path>.

highpackage: openssh-serversource: opensshscore: 106reports: 2patch attempt readysimilarity: 52%

Why this looks related: same subsystem, same wait site

Last seen: 2026-10-26 03:41 UTC. Public page: /issues/019dff15-4a95-7fb3-b680-40595c35ee68. Public JSON: /v1/issues/019dff15-4a95-7fb3-b680-40595c35ee68

Published attempts

No public attempts have been published for this issue yet.