Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug][macOS/M4 Pro] 2026.4.29: plugin staging + sessions.list exhaust event loop [1 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#75968•Fetched 2026-05-03 04:43:44
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
2
Author
260608975260608975
Participants
260608975260608975clawsweeper[bot]clawsweeper[bot]
Timeline (top)
closed ×1commented ×1

Since 2026.4.29, every inbound message triggers full plugin runtime-dep staging (~16s) synchronously. Control UI polls sessions.list every few seconds (each call takes 2.5-3s and fully materializes transcripts). The combined effect blocks the Node.js event loop continuously, causing WebSocket disconnects (code 1006) and total gateway unresponsiveness.

Root Cause

Since 2026.4.29, every inbound message triggers full plugin runtime-dep staging (~16s) synchronously. Control UI polls sessions.list every few seconds (each call takes 2.5-3s and fully materializes transcripts). The combined effect blocks the Node.js event loop continuously, causing WebSocket disconnects (code 1006) and total gateway unresponsiveness.

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (regression, gateway unresponsive)

Summary

Since 2026.4.29, every inbound message triggers full plugin runtime-dep staging (~16s) synchronously. Control UI polls sessions.list every few seconds (each call takes 2.5-3s and fully materializes transcripts). The combined effect blocks the Node.js event loop continuously, causing WebSocket disconnects (code 1006) and total gateway unresponsiveness.

OpenClaw version

2026.4.29 (stable)

Operating system

macOS 25.4.0, Mac Mini M4 Pro (ARM64), Node.js v25.9.0

Steps to reproduce

  1. Gateway runs 2026.4.29 on macOS ARM64
  2. Any message arrives via Feishu (or any channel)
  3. Open Control UI — it continuously polls sessions.list
  4. Plugin runtime deps re-stage on every message (~16s)
  5. Event loop stays saturated; Gateway becomes unresponsive

Observed symptoms

  • eventLoopDelayMaxMs = 4500ms (4.5s) at worst, routinely 3s
  • memory-core: managed dreaming cron could not be reconciled (cron service unavailable) — retry loop consuming resources
  • WebSocket code 1006 disconnects
  • npx spawn ENOENT (playwright MCP fails, secondary symptom)

Related issues/PRs

  • #75831 (fix merged, not yet released) — fix(sessions): persist normalization + defer lazy plugin runtime-dep installs
  • #75752 — Regression: 2026.4.29 adds 30-100s pre-response latency
  • #75703 — Gateway WS handler CPU-spin starvation on ARM64 (4.26-4.29)

extent analysis

TL;DR

The most likely fix is to apply the fix from #75831, which persists normalization and defers lazy plugin runtime-dep installs, to prevent synchronous plugin runtime-dep staging on every inbound message.

Guidance

  • Verify that the issue is caused by the synchronous plugin runtime-dep staging by checking the event loop delay and memory usage when the Control UI polls sessions.list.
  • Consider temporarily reducing the frequency of the Control UI polls to mitigate the blocking of the Node.js event loop.
  • Review the related issues #75752 and #75703 to ensure that the fix does not introduce new regressions, especially on ARM64 architectures.
  • Test the fix in a staging environment before applying it to production to ensure that it resolves the issue without introducing new problems.

Example

No code snippet is provided as the issue does not contain sufficient information to create a minimal example.

Notes

The fix from #75831 is not yet released, so it may need to be cherry-picked or applied manually. Additionally, the issue may be specific to the macOS ARM64 environment, so testing on other platforms may be necessary.

Recommendation

Apply the workaround by reducing the frequency of the Control UI polls or applying the fix from #75831, as it is likely to resolve the issue and prevent the gateway from becoming unresponsive.

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…
#pipeline error#runtime error#dependency conflict#environment setup#docker 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 [Bug][macOS/M4 Pro] 2026.4.29: plugin staging + sessions.list exhaust event loop [1 comments, 2 participants]