Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Regression: openclaw-tui pegs 100% CPU on launch (2026.5.19-beta.1, refs #75289) [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#83974•Fetched 2026-05-20 03:45:42
View on GitHub
Comments
3
Participants
2
Timeline
7
Reactions
1
Author
DevZenProDevZenPro
Participants
clawsweeper[bot]clawsweeper[bot]DevZenProDevZenPro
Timeline (top)
commented ×3mentioned ×2subscribed ×2

openclaw-tui immediately pegs a full CPU core on launch and ignores SIGTERM (requires SIGKILL). This appears to be a regression of #75289, which was closed/completed on 2026-05-15 but is now reproducing on 2026.5.19-beta.1.

Root Cause

openclaw-tui immediately pegs a full CPU core on launch and ignores SIGTERM (requires SIGKILL). This appears to be a regression of #75289, which was closed/completed on 2026-05-15 but is now reproducing on 2026.5.19-beta.1.

Code Example

ops  16030  108  2.1  2463420  720260  pts/1  Rl+  20:53  0:29 openclaw-tui
RAW_BUFFERClick to expand / collapse

Summary

openclaw-tui immediately pegs a full CPU core on launch and ignores SIGTERM (requires SIGKILL). This appears to be a regression of #75289, which was closed/completed on 2026-05-15 but is now reproducing on 2026.5.19-beta.1.

Environment

  • OpenClaw: 2026.5.19-beta.1 (ba9034b) (npm global)
  • Node.js: v24.12.0
  • npm: 11.6.2
  • OS: Ubuntu 24.04.4 LTS, kernel 6.17.0-23-generic, x86_64
  • Shell: zsh

Repro

  1. Start the gateway (running --port 18789 here).
  2. In another terminal: openclaw tui
  3. TUI launches and the openclaw-tui child immediately pegs a full core.

Reproduced both with openclaw tui and openclaw tui --deliver — same behavior either way, so the --deliver flag is not implicated.

Observed

MetricValue
CPU106–108% (one full core, sustained)
RSS~720–738 MB
SIGTERM (kill <pid>)ignored — process survives
SIGKILL (kill -9 <pid>)terminates

Sample ps snapshot:

ops  16030  108  2.1  2463420  720260  pts/1  Rl+  20:53  0:29 openclaw-tui

System load average jumps from ~0.8 → 3+ while the TUI is running, and recovers immediately on SIGKILL.

Related

  • #75289 (closed/completed 2026-05-15) — matches symptoms exactly: 100% CPU per openclaw-tui process, ignores SIGTERM, requires SIGKILL. Locked, so filing fresh.
  • #83560 (open, P1, impact:crash-loop) — openclaw configure flow leaving a high-CPU child process. Similar "stuck child" shape but a different entry point.
  • #62484 (open) — triggers only on openclaw tui -h via sync banner-config-lite.ts import deadlock. Distinct from this repro (no -h used).

Offer

Happy to grab a strace -c or perf sample on the spinning PID if it'd help narrow it down.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#batch processing#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Regression: openclaw-tui pegs 100% CPU on launch (2026.5.19-beta.1, refs #75289) [3 comments, 2 participants]