Runaway CPU investigation for qemu-arm: unknown userspace loop at unresolved offset in qemu-arm

Representative thread backtrace

• Command: /usr/bin/qemu-arm /bin/sh /bin/sh -c echo $CI_SCRIPT | base64 -d | /bin/sh -e
• 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 0x00007f5ee08d430d in ?? () and 1 thread(s) around 0x00007f5ee0be73c9 in ?? ()
• Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: "target:<path>": could not open as an executable file: Input<path> error. warning: `target:<path>': can't open to read symbols: Input<path> error. warning: Could not load vsyscall page because no executable was specified warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container.
• Repeated loop: futex -> wait4
• Top syscalls: futex x1, wait4 x1
• Package: qemu-user 1:11.1.2+ds-3
• Kernel: 7.1.8+deb14.1-amd64
• Distribution: debian

0x00007f5ee08d430d in ?? ()
0x00007ffec28476f0 in ?? ()
0x00007f5ee09c0d5e in ?? ()
0x0000000000000001 in ?? ()
0x000055558b31c8a0 in ?? ()
0x000055558b318e80 in ?? ()
0x00007f5ee141e5a0 in ?? ()
0x00007f5ee1291a80 in ?? ()