Public issue detail

Runaway CPU investigation for perl: busy poll at Perl_mg_find

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

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

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 0x00007f37a376a7d2 in ?? () from target:<path>
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: pselect6 -> pselect6 -> pselect6
  • Top syscalls: pselect6 x4
  • Package: perl-base 5.40.1-7+b1
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007f37a376a7d2 in ?? () from target:<path>
0x00007f37a376a7ed in ?? () from target:<path>
0x00007f37a37ea6cf in select () from target:<path>
0x0000559c21717ee4 in ?? ()
0x0000559c21779496 in Perl_runops_standard ()
0x0000559c2165fb85 in perl_run ()
0x0000559c216325ae 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 Perl_runops_standard, with repeated pselect6 x4.

highpackage: perl-basesource: perlscore: 106reports: 3patch attempt readysimilarity: 99%

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

Last seen: 2026-06-10 02:23 UTC. Public page: /issues/019d4017-20f8-7752-9734-0bcd71623118. Public JSON: /v1/issues/019d4017-20f8-7752-9734-0bcd71623118

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

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-06-10 02:24 UTC. Public page: /issues/019dc199-535d-7c90-9b68-f6459f9c134d. Public JSON: /v1/issues/019dc199-535d-7c90-9b68-f6459f9c134d

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: 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-06-05 21:37 UTC. Public page: /issues/019e9492-ba96-7f00-9599-ad575e4de4ca. Public JSON: /v1/issues/019e9492-ba96-7f00-9599-ad575e4de4ca

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: 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-06-04 21:19 UTC. Public page: /issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321. Public JSON: /v1/issues/019e8f7a-7c69-7b52-9e9e-6890b1ecf321

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

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

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: 1similarity: 77%

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

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

Published attempts

No public attempts have been published for this issue yet.