Public issue detail

Runaway CPU investigation for docker: unknown userspace loop at unresolved offset in docker

docker is stuck in a likely unclassified userspace loop: 8.08% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x0000562e5220b603 in _cgo_topofstack () and 1 thread(s) around 0x0000562e5220b603 in _cgo_topofstack ().

highpackage: docker-clisource: docker.ioscore: 106reports: 1

Last seen: 2026-10-24 03:10 UTC. Public JSON: /v1/issues/01a16baa-a7c4-7123-8633-b284c58f970e

Technical snapshot

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

Representative thread backtrace

  • Command: /usr/bin/docker run --name=osgeo-woodie-agent --restart=unless-stopped --security-opt apparmor=unconfined --group-add=132 --volume=/var/run/docker.sock:/var/run/docker.sock --volume=/etc/woodpecker/:/etc/woodpecker/ --env-file=/etc/woodpecker/osgeo-agent.env --env=WOODPECKER_RETRY_TIMEOUT=0 osgeo-woodie-agent:v3.15.0-apparmor1
  • 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 0x0000562e5220b603 in _cgo_topofstack () and 1 thread(s) around 0x0000562e5220b603 in _cgo_topofstack ()
  • Contention signals: gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory.
  • Repeated loop: futex -> futex -> futex
  • Top syscalls: futex x19, epoll_pwait x1, restart_syscall x1
  • Package: docker-cli 28.5.2+dfsg4-4
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x0000562e5220b603 in _cgo_topofstack ()
0x0000562e521c5d90 in ?? ()
0x0000562e53dbfdb8 in ?? ()
0x0000000000000080 in ?? ()
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 ollama: unknown userspace loop at unresolved offset in ollama

possible duplicate

ollama is stuck in a likely unclassified userspace loop: 12.27% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x000055c5c39ed143 in ?? () and 1 thread(s) around 0x000055c5c39ed143 in ?? ().

highscore: 106reports: 3successful triagesimilarity: 99%

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

Last seen: 2026-10-05 15:22 UTC. Public page: /issues/019dd7a7-430c-79a0-bc5b-7549a044b3fc. Public JSON: /v1/issues/019dd7a7-430c-79a0-bc5b-7549a044b3fc

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

possible duplicate

qemu-arm is stuck in a likely unclassified userspace loop: 2.78% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f5ee08d430d in ?? () and 1 thread(s) around 0x00007f5ee0be73c9 in ?? ().

highpackage: qemu-usersource: qemuscore: 106reports: 1similarity: 83%

Why this looks related: same classification, same subsystem

Last seen: 2026-10-21 04:19 UTC. Public page: /issues/019f9e15-6812-7222-920d-b38631b98fd2. Public JSON: /v1/issues/019f9e15-6812-7222-920d-b38631b98fd2

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

possible duplicate

qemu-s390x is stuck in a likely unclassified userspace loop: 3.25% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007fd4b10cf98d in ?? () and 1 thread(s) around 0x00007fd4b13582c9 in ?? ().

highpackage: qemu-usersource: qemuscore: 106reports: 1similarity: 82%

Why this looks related: same classification, same subsystem

Last seen: 2026-10-24 01:49 UTC. Public page: /issues/019f9eb7-d046-7732-ad3b-eaab1885c0e4. Public JSON: /v1/issues/019f9eb7-d046-7732-ad3b-eaab1885c0e4

Runaway CPU investigation for dockerd: socket churn at mem_cgroup_handle_over_high

possible duplicate

dockerd is stuck in a likely socket churn loop: 34.73% of sampled CPU passed through mem_cgroup_handle_over_high, with repeated thread backtraces show 1 thread(s) around 0x000056124fea7023 in ?? () and 1 thread(s) around 0x000056124fea7023 in ?? ().

highpackage: docker.iosource: docker.ioscore: 106reports: 2similarity: 57%

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

Last seen: 2026-10-25 16:39 UTC. Public page: /issues/019deedb-94d6-7423-a4c3-f13abd24a2cb. Public JSON: /v1/issues/019deedb-94d6-7423-a4c3-f13abd24a2cb

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.