openclaw - 💡(How to fix) Fix [Bug]: CPU Regression: v2026.4.25 Cold Plugin Registry Refactor Fails to Separate Cold/Hot Paths [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#73036Fetched 2026-04-28 06:28:21
View on GitHub
Comments
3
Participants
2
Timeline
5
Reactions
1
Timeline (top)
commented ×3closed ×1labeled ×1

After upgrading to v2026.4.25, every inbound message causes the openclaw-gateway process to immediately spike to sustained ~1 core (24-core machine) and stays elevated for the full duration of message processing. This did NOT occur on v2026.4.24, where CPU returned to near-idle (~5-10%) between messages.

Root Cause

After upgrading to v2026.4.25, every inbound message causes the openclaw-gateway process to immediately spike to sustained ~1 core (24-core machine) and stays elevated for the full duration of message processing. This did NOT occur on v2026.4.24, where CPU returned to near-idle (~5-10%) between messages.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to v2026.4.25, every inbound message causes the openclaw-gateway process to immediately spike to sustained ~1 core (24-core machine) and stays elevated for the full duration of message processing. This did NOT occur on v2026.4.24, where CPU returned to near-idle (~5-10%) between messages.

Steps to reproduce

  1. Upgrade from v2026.4.24 to v2026.4.25
  2. Send any message to the gateway (via webchat or any channel)
  3. Observe openclaw-gateway CPU jumps to 100%+ and stays high until response completes

Expected behavior

On v2026.4.24, inbound messages caused ~20-50% CPU briefly then dropped to idle.

Actual behavior

After upgrading to v2026.4.25, the openclaw-gateway process exhibits the following:

  1. Idle CPU jumps from ~5-10% to ~20-30%
  2. On any inbound message, CPU immediately spikes to ~1 core sustained (100%+ on a 24-core machine)
  3. CPU stays elevated for the full duration of message processing, never dropping below ~100% while active
  4. V8 CPU profiler shows 58%+ internal overhead (GC ~26%, StrictEqual ~13%, Megamorphic IC ~11%)
  5. Rollback to v2026.4.24 resolves all symptoms — normal CPU behavior restored

OpenClaw version

2026.4.25 (aa36ee6)

Operating system

Ubuntu 24.04.4

Install method

No response

Model

DeepSeekV4

Provider / routing chain

N/A — this is not a request/routing issue. The regression is in the plugin registry cold/hot path separation.

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The most likely fix is to rollback to version v2026.4.24, as it has been confirmed to resolve the CPU spike issue.

Guidance

  • Verify that the issue is indeed caused by the upgrade to v2026.4.25 by testing with different versions.
  • Check the V8 CPU profiler output to understand the internal overhead causing the CPU spike, specifically the GC, StrictEqual, and Megamorphic IC components.
  • Investigate the changes made in v2026.4.25 that could be causing the regression, focusing on the plugin registry cold/hot path separation.
  • Consider opening an issue with the OpenClaw developers to report the regression and request a fix.

Example

No code snippet is provided as the issue is related to a version regression and not a specific code block.

Notes

The issue seems to be specific to the v2026.4.25 version of OpenClaw, and rolling back to v2026.4.24 resolves the issue. However, this may not be a permanent solution, and the root cause should be investigated.

Recommendation

Apply workaround: Rollback to version v2026.4.24, as it has been confirmed to resolve the CPU spike issue. This is a temporary solution until the root cause is identified and fixed.

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

On v2026.4.24, inbound messages caused ~20-50% CPU briefly then dropped to idle.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING