- Message response time should be < 5 seconds - eventLoopDelayP99Ms should be < 1000ms - Single message processing should be < 2 seconds - Direct MiniMax API calls and Gateway proxy should both work normally

openclaw - 💡(How to fix) Fix [Bug] OpenClaw 2026.4.29 Windows: 162s eventLoopDelay blocking Gateway [1 comments, 2 participants]

openclaw2026-05-02 10:43:45

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

openclaw/openclaw#76041•Fetched 2026-05-03 04:43:02

View on GitHub

Comments

Participants

Timeline

Reactions

Author

gaozhaohe050-hue

Participants

clawsweeper[bot]

gaozhaohe050-hue

Timeline (top)

labeled ×2closed ×1commented ×1unsubscribed ×1

Gateway eventLoop completely blocked on every message. Single "状态如何" query takes 8 minutes to respond. eventLoopDelayP99Ms=162403.5ms, core-plugin-tools=162299ms, system-prompt=81039ms, stream-setup=77501ms. MiniMax API direct call responds in milliseconds, but Gateway HTTP endpoint times out.

Root Cause

Fix Action

Fix / Workaround

[agent/embedded] model-resolution:33096ms, auth:36173ms, attempt-dispatch:51548ms, totalMs=120822
[agent/embedded] core-plugin-tools:162299ms, system-prompt:81039ms, stream-setup:77501ms, totalMs=362272
[diagnostic] eventLoopDelayP99Ms=162403.5, eventLoopUtilization=1
[diagnostic] stuck session age=516s queueDepth=1

Affected users/systems: 所有通过 Gateway 交互的用户
Severity: Critical（完全功能故障）
Frequency: 100% (每次消息必现)
Consequence: Gateway 完全无法用于实时交互，用户等待 8 分钟无响应
Workaround: 只能直接调用 API 绕过 Gateway

Code Example

[agent/embedded] model-resolution:33096ms, auth:36173ms, attempt-dispatch:51548ms, totalMs=120822
[agent/embedded] core-plugin-tools:162299ms, system-prompt:81039ms, stream-setup:77501ms, totalMs=362272
[diagnostic] eventLoopDelayP99Ms=162403.5, eventLoopUtilization=1
[diagnostic] stuck session age=516s queueDepth=1

直接调用测试证明问题不在 MiniMax：
- Invoke-RestMethod https://api.minimaxi.com/v1/models → 秒回成功
- Invoke-RestMethod http://127.0.0.1:18789/v1/chat/completions → 超时

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

Summary

Steps to reproduce

Install OpenClaw 2026.4.29 on Windows 10/11
Configure MiniMax API Key (direct access, works fine when tested directly)
Start Gateway: openclaw gateway start
Wait 28-44 seconds for Gateway to come online
Send any message via WebSocket UI or HTTP API
Observe: 8 minutes pass before any response
Check diagnostic: eventLoopDelayP99Ms = 162403.5ms

Expected behavior

Message response time should be < 5 seconds
eventLoopDelayP99Ms should be < 1000ms
Single message processing should be < 2 seconds
Direct MiniMax API calls and Gateway proxy should both work normally

Actual behavior

Message response time: 8 minutes (480 seconds)
eventLoopDelayP99Ms: 162403.5ms (162 seconds)
Single message processing: 362272ms total (362 seconds)
eventLoopUtilization: 1 (100% event loop blocked)
Gateway HTTP proxy endpoint: timeout
WebSocket: timeout

OpenClaw version

2026.4.29 (a448042)

Operating system

Windows 10/11 (DESKTOP-TF7GD57), Node.js v24.15.0

Install method

npm global install

Model

minimax/MiniMax-M2.7

Provider / routing chain

openclaw -> minimax (direct API Key)

Additional provider/model setup details

MiniMax API Key direct connection via api.minimaxi.com API Key: sk-cp-... (已配置，直连测试正常) 配置状态：gateway.mode=local, 仅启用 minimax 插件，bonjour 已禁用插件数量：~160 个插件在 dist/extensions/ 目录

Logs, screenshots, and evidence

[agent/embedded] model-resolution:33096ms, auth:36173ms, attempt-dispatch:51548ms, totalMs=120822
[agent/embedded] core-plugin-tools:162299ms, system-prompt:81039ms, stream-setup:77501ms, totalMs=362272
[diagnostic] eventLoopDelayP99Ms=162403.5, eventLoopUtilization=1
[diagnostic] stuck session age=516s queueDepth=1

直接调用测试证明问题不在 MiniMax：
- Invoke-RestMethod https://api.minimaxi.com/v1/models → 秒回成功
- Invoke-RestMethod http://127.0.0.1:18789/v1/chat/completions → 超时

Impact and severity

Affected users/systems: 所有通过 Gateway 交互的用户 Severity: Critical（完全功能故障） Frequency: 100% (每次消息必现) Consequence: Gateway 完全无法用于实时交互，用户等待 8 分钟无响应 Workaround: 只能直接调用 API 绕过 Gateway

Additional information

Last known good version: 未知（首次安装 2026.4.29） First known bad version: 2026.4.29（首次安装既现）相关已知 Issues:

#64419: Gateway startup clobbers config (Open)
#70096: doctor --fix rewrites valid config (Open) 核心问题：dist/extensions/ 下约 160 个插件全部被扫描初始化，导致主线程阻塞 162 秒

extent analysis

TL;DR

The Gateway event loop is completely blocked due to the initialization of approximately 160 plugins in the dist/extensions/ directory, causing an 8-minute delay in responding to messages.

Guidance

Investigate the plugin initialization process to identify the cause of the blockage, focusing on the core-plugin-tools and system-prompt components, which are taking 162299ms and 81039ms, respectively.
Consider optimizing or disabling unnecessary plugins to reduce the initialization time and prevent event loop blockage.
Verify the configuration of the gateway.mode and ensure that only the necessary plugins are enabled, as the current setup has bonjour disabled but still has a large number of plugins.
Check the eventLoopUtilization and queueDepth metrics to monitor the event loop's performance and adjust the plugin initialization process accordingly.

Example

No code snippet is provided, as the issue is related to plugin initialization and event loop blockage, which requires a more in-depth investigation of the system configuration and plugin management.

Notes

The issue is critical, affecting all users interacting with the Gateway, and a workaround is available by directly calling the API, bypassing the Gateway. However, a proper fix requires identifying and addressing the root cause of the plugin initialization blockage.

Recommendation

Apply a workaround by optimizing or disabling unnecessary plugins to reduce the initialization time and prevent event loop blockage, as the current version (2026.4.29) has a critical issue that needs to be addressed.

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?

FAQ

Expected behavior

Message response time should be < 5 seconds
eventLoopDelayP99Ms should be < 1000ms
Single message processing should be < 2 seconds
Direct MiniMax API calls and Gateway proxy should both work normally

#api #optimization #mixed precision #training loop #device allocation

Still need to ship something?

×6

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

openclaw - 💡(How to fix) Fix [Bug] OpenClaw 2026.4.29 Windows: 162s eventLoopDelay blocking Gateway [1 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Root Cause

Fix Action

Fix / Workaround

Code Example

Bug type

Beta release blocker

Summary

Steps to reproduce

Expected behavior

Actual behavior

OpenClaw version

Operating system

Install method

Model

Provider / routing chain

Additional provider/model setup details

Logs, screenshots, and evidence

Impact and severity

Additional information

extent analysis

TL;DR

Guidance

Example

Notes

Recommendation

FAQ

Expected behavior

Still need to ship something?

RELATED_DISCOVERY

TRENDING