#**Bug: Gateway pegs CPU at 100%+ on ARM64 (Raspberry Pi 5)**

1 messages · Page 1 of 1 (latest)

cobalt badger
#

Bug: Gateway pegs CPU at 100%+ on ARM64 (Raspberry Pi 5)

Platform: Raspberry Pi 5 (8GB) — ARM64
OS: Ubuntu Desktop 25.10
OpenClaw version: [2026.4.26]

Description:
The gateway process consistently pegs CPU at 100%+ on ARM64 architecture. This causes two main issues:

  • The TUI becomes completely unusable (frozen/unresponsive)
  • Bot responses are significantly slower than expected

What's working:

  • Gateway starts and runs
  • Discord connection is stable
  • Jobs/automation run fine
  • Bot responds to messages (just very slowly)

What's broken:

  • TUI is unusable due to CPU load
  • Response latency is much higher than on x86

Workarounds tried:

  • Clean reinstall
  • Disabled Bonjour/mDNS (discovery.mdns.mode=off)
  • Set timeoutSeconds=120 for model provider
  • Set Restart=no in systemd to prevent duplicate processes

None of these resolved the CPU issue — they addressed other problems but the ARM64 CPU bug persists.

Suspected cause: Something in the gateway process doesn't behave well on ARM64 — possibly a busy loop or polling interval issue.

Happy to provide logs or test any fixes.

lean sunBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

north sigilBOT
#

This is a solid bug report — thanks. Since you’re already on 2026.4.26 and tried the obvious config workarounds, this probably needs maintainer-level profiling rather than more config guessing.

Please file this as a GitHub issue: https://github.com/openclaw/openclaw/issues

Useful extra data to attach:

openclaw status --all
openclaw gateway status --deep
openclaw --version
uname -a
node -p "process.platform + ' ' + process.arch + ' ' + process.version"
pgrep -af 'openclaw|node'

If you can tolerate restarting the gateway briefly, the most useful thing would be a Node CPU profile while it’s pegged: