Public issue detail

Runaway CPU investigation for llmfit: unknown userspace loop at <&ratatui_core::text::span::Span as ratatui_core::widgets::widget::Widg…

llmfit is stuck in a likely unclassified userspace loop: 10.54% of sampled CPU passed through <&ratatui_core::text::span::Span as ratatui_core::widgets::wi..., with repeated thread backtraces show 1 thread(s) around 0x00007fb47b894bf6 in sccp ().

highscore: 106reports: 1

Last seen: 2026-07-08 11:50 UTC. Public JSON: /v1/issues/019ed1fd-2fcf-7a10-b2e6-e2656b4f763e

Technical snapshot

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

Representative thread backtrace

  • Command: llmfit
  • Why Fixer classified it this way: The process is demonstrably CPU-hot, but the current syscall and symbol sample does not point to a single dominant loop family yet.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007fb47b894bf6 in sccp ()
  • Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: mmap -> mmap -> mmap
  • Top syscalls: mmap x9927, munmap x9927, epoll_pwait x81, close x80
  • Kernel: 6.17.10+deb14-amd64
  • Distribution: debian
0x00007fb47b894bf6 in sccp ()
0x00007fb47b88a55a in epoll_pwait ()
0x0000000000000000 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 postgres: unknown userspace loop at do_fault

possible duplicate

postgres is stuck in a likely unclassified userspace loop: 50.00% of sampled CPU passed through do_fault, with repeated thread backtraces show 1 thread(s) around 0x00007f33aba9a7d2 in ?? () from target:<path>.

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

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

Last seen: 2026-07-08 12:09 UTC. Public page: /issues/019f077a-7a30-78d1-b552-06c90a00dbb0. Public JSON: /v1/issues/019f077a-7a30-78d1-b552-06c90a00dbb0

Runaway CPU investigation for redis-check-rdb: dbus spin at unresolved offset in libc.so.6

possible duplicate

redis-check-rdb is stuck in a likely dbus spin loop: 7.11% 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: 1similarity: 46%

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-27 16:08 UTC. Public page: /issues/019f09b6-00ac-7ed1-b030-4d766182ca1e. Public JSON: /v1/issues/019f09b6-00ac-7ed1-b030-4d766182ca1e

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

Why this looks related: 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: 46%

Why this looks related: 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 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: 45%

Why this looks related: 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

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.