Public issue detail

Runaway CPU investigation for qbittorrent: dbus spin at unresolved offset in libgcc_s.so.1

qbittorrent is stuck in a likely dbus spin loop: 14.10% of sampled CPU passed through [.] 0x0000000000009532, with repeated recvfrom x2882, epoll_wait x2087, sendto x1748.

highpackage: qbittorrentsource: qbittorrentscore: 106reports: 1

Last seen: 2026-04-03 22:55 UTC. Public JSON: /v1/issues/019d3bbe-9bd3-7e71-b146-f7ab62c90432

Technical snapshot

This is the stack-shaped slice and hot path Fixer captured while the process was spinning.

Sampled wait stack

Command: /usr/bin/qbittorrent -session 10dfd0c2e0000176308007300000023100008_1763739085_151412
Why Fixer classified it this way: The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.
Wait site: poll_schedule_timeout.constprop.0
Hot path: (deleted) [.] 0x0000000000009532 (14.10% sampled CPU)
Repeated loop: epoll_wait -> recvfrom -> recvfrom
Top syscalls: recvfrom x2882, epoll_wait x2087, sendto x1748, epoll_ctl x1343
Package: qbittorrent

poll_schedule_timeout.constprop.0
do_poll.constprop.0
do_sys_poll
__x64_sys_ppoll
x64_sys_call
do_syscall_64
entry_SYSCALL_64_after_hwframe

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 libc.so.6

possible duplicate

python3.13 is stuck in a likely busy poll loop: 6.41% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fdd05c9b72e in ?? () and 1 thread(s) around 0x00007fdd05c9b72e in ?? ().

highpackage: python3.13-minimalsource: python3.13score: 106reports: 3patch attempt readysimilarity: 52%

Why this looks related: same subsystem, same wait site

Last seen: 2026-07-09 19:56 UTC. Public page: /issues/019d7cef-46dd-7541-b939-9ba6872fbf76. Public JSON: /v1/issues/019d7cef-46dd-7541-b939-9ba6872fbf76

Runaway CPU investigation for python3.13: busy poll at unresolved offset in python3.13

possible duplicate

python3.13 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 0x00007f091ce537d2 in ?? () from target:<path>.

highpackage: python3.13-minimalsource: python3.13score: 106reports: 2similarity: 51%

Why this looks related: same subsystem, same wait site

Last seen: 2026-07-02 03:18 UTC. Public page: /issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51. Public JSON: /v1/issues/019dc2a0-9ae7-7f42-8f59-415fe22abe51

Runaway CPU investigation for sshd-session: unknown userspace loop at unresolved offset in libc.so.6

possible duplicate

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

highpackage: openssh-serversource: opensshscore: 106reports: 2similarity: 48%

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-27 21:56 UTC. Public page: /issues/019db544-ab14-73a0-b91c-7276539c4cf4. Public JSON: /v1/issues/019db544-ab14-73a0-b91c-7276539c4cf4

Runaway CPU investigation for sshd-session: unknown userspace loop at unresolved offset in libpam.so.0.85.1

possible duplicate

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

highpackage: openssh-serversource: opensshscore: 106reports: 1similarity: 47%

Why this looks related: same subsystem, same wait site

Last seen: 2026-06-27 08:47 UTC. Public page: /issues/019f056b-3325-7161-9797-4ddd63b6b535. Public JSON: /v1/issues/019f056b-3325-7161-9797-4ddd63b6b535

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 failed patch attempts

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

Most common blockers

patch proposal did not complete cleanly (1 attempt)

Published attempts

failed patch attempt

patch

qbittorrent likely remains stuck in a dbus spin loop. The diagnosis was captured, but the patch proposal did not complete cleanly.

state: failedcreated: 2026-03-29 15:29 UTCvalidation: failed

Why it stopped

patch proposal did not complete cleanly

Collected context

This older failed attempt predates structured patch failure capture, so Fixer only retained the diagnosis and workspace context.
Subsystem: runaway-process
Diagnosis family: dbus-spin
Hot path: (deleted) [.] 0x0000000000009532
Command: /usr/bin/qbittorrent -session 10dfd0c2e0000176308007300000023100008_1763739085_151412
Source package: qbittorrent
Workspace source: debian-source
Workspace acquisition: Fetched Debian source package via apt-get source.
Homepage: https://www.qbittorrent.org/
Implicated packages: libtorrent-rasterbar2.0t64, linux-image-6.17.0-14-generic

The trace is dominated by DBus-style socket activity and DBus-related symbols, which looks like a message-loop spin.