openclaw - 💡(How to fix) Fix [Bug]: TUI freezes/starves input and pegs CPU at ~100% on Linux/KDE [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#75829Fetched 2026-05-02 05:29:25
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Timeline (top)
labeled ×2closed ×1commented ×1

OpenClaw: 2026.4.29 (a448042) OS: Linux 7.0.2-2-cachyos x64 DE/terminal: KDE/Wayland, Konsole Node tested:

  • v25.9.0 initially
  • v22.22.2 via fnm/systemd override

Issue: openclaw tui and openclaw tui --local render, but input is effectively frozen/starved. A few typed characters may appear after several seconds. openclaw-tui processes peg ~100% CPU and sometimes remain as defunct processes after kill/close.

What we tried:

  • Reinstalled OpenClaw
  • Switched gateway runtime from Node 25 to Node 22.22.2
  • Disabled Bonjour
  • Disabled nonessential plugins: active-memory, browser, phone-control, talk-voice, discord
  • Disabled acpx for test
  • Tried fresh session: openclaw tui --local --session rescue --history-limit 0
  • Gateway still shows event_loop_delay warnings, but TUI itself also spins at ~100% CPU

Useful evidence:

  • ps showed openclaw-tui at ~100% CPU
  • gateway logs showed repeated diagnostic liveness warning: event_loop_delay
  • minimal plugin gateway still loaded only device-pair/file-transfer/memory-core, but TUI remained unusable

Root Cause

OpenClaw: 2026.4.29 (a448042) OS: Linux 7.0.2-2-cachyos x64 DE/terminal: KDE/Wayland, Konsole Node tested:

  • v25.9.0 initially
  • v22.22.2 via fnm/systemd override

Issue: openclaw tui and openclaw tui --local render, but input is effectively frozen/starved. A few typed characters may appear after several seconds. openclaw-tui processes peg ~100% CPU and sometimes remain as defunct processes after kill/close.

What we tried:

  • Reinstalled OpenClaw
  • Switched gateway runtime from Node 25 to Node 22.22.2
  • Disabled Bonjour
  • Disabled nonessential plugins: active-memory, browser, phone-control, talk-voice, discord
  • Disabled acpx for test
  • Tried fresh session: openclaw tui --local --session rescue --history-limit 0
  • Gateway still shows event_loop_delay warnings, but TUI itself also spins at ~100% CPU

Useful evidence:

  • ps showed openclaw-tui at ~100% CPU
  • gateway logs showed repeated diagnostic liveness warning: event_loop_delay
  • minimal plugin gateway still loaded only device-pair/file-transfer/memory-core, but TUI remained unusable
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

OpenClaw: 2026.4.29 (a448042) OS: Linux 7.0.2-2-cachyos x64 DE/terminal: KDE/Wayland, Konsole Node tested:

  • v25.9.0 initially
  • v22.22.2 via fnm/systemd override

Issue: openclaw tui and openclaw tui --local render, but input is effectively frozen/starved. A few typed characters may appear after several seconds. openclaw-tui processes peg ~100% CPU and sometimes remain as defunct processes after kill/close.

What we tried:

  • Reinstalled OpenClaw
  • Switched gateway runtime from Node 25 to Node 22.22.2
  • Disabled Bonjour
  • Disabled nonessential plugins: active-memory, browser, phone-control, talk-voice, discord
  • Disabled acpx for test
  • Tried fresh session: openclaw tui --local --session rescue --history-limit 0
  • Gateway still shows event_loop_delay warnings, but TUI itself also spins at ~100% CPU

Useful evidence:

  • ps showed openclaw-tui at ~100% CPU
  • gateway logs showed repeated diagnostic liveness warning: event_loop_delay
  • minimal plugin gateway still loaded only device-pair/file-transfer/memory-core, but TUI remained unusable

Steps to reproduce

run openclaw tui

Expected behavior

TUI should accept input normally and idle without pegging CPU.

Actual behavior

TUI renders but becomes extremely laggy/starved, input delayed by seconds then unresponsive, CPU pegged.

OpenClaw version

2026.4.29 (a448042)

Operating system

Linux 7.0.2-2-cachyos x64

Install method

npm global install

Model

openai-codex/gpt-5.5 via OAuth

Provider / routing chain

Gateway/local embedded agent → openai-codex/gpt-5.5 via OAuth

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

openclaw-tui-bug-report-diagnostics.txt

extent analysis

TL;DR

The issue can be mitigated by investigating and addressing the event_loop_delay warnings in the gateway logs, which may be causing the openclaw-tui process to peg at 100% CPU.

Guidance

  • Investigate the event_loop_delay warnings in the gateway logs to understand the root cause of the delay.
  • Verify if the issue persists when running openclaw tui with the --local flag and a fresh session using openclaw tui --local --session rescue --history-limit 0.
  • Check the system resources and CPU usage of other processes to ensure that the issue is not caused by system-wide resource constraints.
  • Review the openclaw-tui-bug-report-diagnostics.txt file for any additional clues or error messages that may indicate the cause of the issue.

Example

No code snippet is provided as the issue is related to a specific application and its configuration.

Notes

The issue may be related to the Node version or the gateway configuration, but more investigation is needed to determine the root cause. The provided diagnostic file may contain additional information that can help identify the issue.

Recommendation

Apply workaround: Investigate and address the event_loop_delay warnings in the gateway logs, as this may be the primary cause of the issue.

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…

FAQ

Expected behavior

TUI should accept input normally and idle without pegging CPU.

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 [Bug]: TUI freezes/starves input and pegs CPU at ~100% on Linux/KDE [1 comments, 2 participants]