openclaw - 💡(How to fix) Fix [Bug]: openclaw doctor becomes very slow in 2026.5.22

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…

After upgrading from 2026.5.20 to 2026.5.22. Openclaw doctor uses 100% CPU and becomes unresponsive making it impossible to complete the upgrade. An strace shows that openclaw doctor appears to be scanning all of the node modules before continuing. This is not an issue in 2026.5.20

Root Cause

After upgrading from 2026.5.20 to 2026.5.22. Openclaw doctor uses 100% CPU and becomes unresponsive making it impossible to complete the upgrade. An strace shows that openclaw doctor appears to be scanning all of the node modules before continuing. This is not an issue in 2026.5.20

Fix Action

Fix / Workaround

Alternatively you can nom upgrade to 2026.5.22 and run openclaw doctor which never comes up with the initial screen while 2026.5.20 brings up the doctor immediately.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading from 2026.5.20 to 2026.5.22. Openclaw doctor uses 100% CPU and becomes unresponsive making it impossible to complete the upgrade. An strace shows that openclaw doctor appears to be scanning all of the node modules before continuing. This is not an issue in 2026.5.20

Steps to reproduce

  1. openclaw update to 2026.5.22
  2. The process stalls at openclaw doctor

Alternatively you can nom upgrade to 2026.5.22 and run openclaw doctor which never comes up with the initial screen while 2026.5.20 brings up the doctor immediately.

Expected behavior

When you run openclaw doctor, it should very quickly bring up the init message.

Actual behavior

There is no response from openclaw doctor even after a minute, and CPU is at 100%. Strace shows that the process appears to be scanning all of the files in the openclaw distribution.

OpenClaw version

2026.5.22

Operating system

Arabian rk3588 device

Install method

No response

Model

openrouter/free

Provider / routing chain

openclaw

Additional provider/model setup details

This is running on a low CPU arm device with a slow flash as disk.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

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

When you run openclaw doctor, it should very quickly bring up the init message.

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]: openclaw doctor becomes very slow in 2026.5.22