This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.
Representative thread backtrace
- Command: /usr/bin/python3 /usr/bin/unattended-upgrade --download-only
- 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 2 thread(s) around __syscall_cancel_arch () at ..<path>:56 and 1 thread(s) around 0x00007fbe346fe8a4 in void CppDeallocPtr<Configuration*>(_object*) () from target:<path>
- Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
- Repeated loop: newfstatat -> newfstatat -> newfstatat
- Top syscalls: newfstatat x166906, lseek x210, read x210, ppoll x2
- Package: python3.14-minimal 3.14.7-4
- Kernel: 7.1.8+deb14.1-amd64
- Distribution: debian
__syscall_cancel_arch () at ..<path>:56
0x00007fbe358d39d4 in __internal_syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:49
0x00007fbe358d3a1d in __syscall_cancel (a1=..., a2=..., a3=..., a4=..., a5=..., a6=..., nr=...) at .<path>:75
0x00007fbe3594845e in __GI_ppoll (fds=..., nfds=..., timeout=..., sigmask=...) at ..<path>:42
0x00007fbe332a447e in g_get_monotonic_time_ns () from target:<path>
0x00007fbe332a4d20 in g_main_context_iteration () from target:<path>
0x00007fbe332a4d71 in g_main_context_iteration () from target:<path>
0x00007fbe332d9ea0 in g_private_set () from target:<path>