Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Windows QClaw gateway exit code 1, WebSocket message delivery failure, crash dumps not uploaded [2 comments, 3 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#68810•Fetched 2026-04-19 15:07:10
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
1528570168315285701683
Participants
1528570168315285701683gongli0929gongli0929Sanjays2402Sanjays2402
Timeline (top)
commented ×2labeled ×2cross-referenced ×1mentioned ×1

QClaw gateway on Windows 11 exits with code 1 on all CLI commands. WeChat channel message delivery intermittently fails with "This operation was aborted". 5 Crashpad crash dumps (33MB each) have not been uploaded to the crash server. Main process memory leaks to 1.5GB.

Error Message

  1. WeChat messages intermittently fail with error: "This operation was aborted". Error during openclaw gateway restart:

Root Cause

QClaw gateway on Windows 11 exits with code 1 on all CLI commands. WeChat channel message delivery intermittently fails with "This operation was aborted". 5 Crashpad crash dumps (33MB each) have not been uploaded to the crash server. Main process memory leaks to 1.5GB.

Code Example

Config warnings from `openclaw help`:
- plugins.entries.imap-smtp-email: plugin not found
- plugins.entries.memory-tencentdb: plugin disabled but config is present
- plugins.entries.openclaw-mem0: plugin disabled but config is present

Error during `openclaw gateway restart`:
- Exec failed (fresh-cr, code 1)
- Exec failed (tidy-har, code 1)

Crashpad reports (un-uploaded):
- 2026-03-28 18:27 | 33.3MB
- 2026-04-02 16:39 | 33.2MB
- 2026-04-03 15:06 | 33.3MB
- 2026-04-04 20:35 | 33.4MB
- 2026-04-10 08:34 | 33.3MB

Note: All log files in logs/main/ are .enc encrypted and cannot be read for diagnostics.
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

QClaw gateway on Windows 11 exits with code 1 on all CLI commands. WeChat channel message delivery intermittently fails with "This operation was aborted". 5 Crashpad crash dumps (33MB each) have not been uploaded to the crash server. Main process memory leaks to 1.5GB.

Steps to reproduce

  1. Install QClaw (OpenClaw Windows distribution) version 2026.3.13 on Windows 11.
  2. Run any openclaw CLI command (e.g., openclaw help, openclaw gateway status). All exit with code 1.
  3. Send messages via WeChat channel. Intermittently observe delivery failure.
  4. Check AppData/Roaming/QClaw/Crashpad/reports/ — 5 crash dumps remain un-uploaded.

Expected behavior

  1. CLI commands should exit with code 0 on success. Config warnings (stale plugin entries) should not cause non-zero exit codes.
  2. WeChat message delivery should succeed reliably.
  3. Crashpad crash dumps should be uploaded to the remote crash server automatically.

Actual behavior

  1. All CLI commands exit with code 1. Stderr shows config warnings about stale plugins (imap-smtp-email, memory-tencentdb, openclaw-mem0).
  2. WeChat messages intermittently fail with error: "This operation was aborted".
  3. 5 Crashpad .dmp files (33MB each, dated 2026-03-28 to 2026-04-10) remain in reports directory — never uploaded.
  4. 9 log rotation files generated today (2026-04-19) indicating frequent gateway restarts.
  5. Main process (PID 23704) consumes 1.5GB RAM. 7 QClaw processes total ~2.5GB.

OpenClaw version

2026.3.13 (61d171a)

Operating system

Windows 11 Pro (10.0.26200 x64)

Install method

QClaw Windows installer (D:\Program Files\QClaw)

Model

qclaw/modelroute

Provider / routing chain

QClaw -> modelroute (managed routing)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Config warnings from `openclaw help`:
- plugins.entries.imap-smtp-email: plugin not found
- plugins.entries.memory-tencentdb: plugin disabled but config is present
- plugins.entries.openclaw-mem0: plugin disabled but config is present

Error during `openclaw gateway restart`:
- Exec failed (fresh-cr, code 1)
- Exec failed (tidy-har, code 1)

Crashpad reports (un-uploaded):
- 2026-03-28 18:27 | 33.3MB
- 2026-04-02 16:39 | 33.2MB
- 2026-04-03 15:06 | 33.3MB
- 2026-04-04 20:35 | 33.4MB
- 2026-04-10 08:34 | 33.3MB

Note: All log files in logs/main/ are .enc encrypted and cannot be read for diagnostics.

Impact and severity

Affected: Windows QClaw users on WeChat channel Severity: High (blocks CLI usage, intermittent message loss, memory leak degrades system) Frequency: CLI exit code 1 is constant (100%). Message delivery failure is intermittent (~30%). Memory growth is progressive. Consequence: Cannot use CLI for management. Scheduled cron tasks and message delivery are unreliable. System memory degradation over time requires manual gateway restarts.

Additional information

  • skill-interceptor plugin keeps re-enabling after QClaw updates, blocking 17 skills despite user repeatedly disabling it
  • lcm.db is 58MB with 5.5MB WAL file
  • 7 QClaw processes running simultaneously (total ~2.5GB)
  • Logs are all .enc encrypted, making user-side diagnostics impossible
  • The stale plugin config entries (imap-smtp-email, memory-tencentdb, openclaw-mem0) may be causing the exit code 1 issue

extent analysis

TL;DR

The QClaw gateway on Windows 11 exits with code 1 on all CLI commands, likely due to stale plugin config entries, and WeChat message delivery intermittently fails, which may be resolved by addressing the plugin issues and memory leaks.

Guidance

  • Investigate and resolve the stale plugin config entries (imap-smtp-email, memory-tencentdb, openclaw-mem0) to prevent exit code 1 issues.
  • Check the skill-interceptor plugin configuration to prevent it from re-enabling and blocking skills.
  • Monitor the memory usage of the QClaw processes and consider optimizing the configuration to prevent memory leaks.
  • Consider decrypting the log files to facilitate diagnostics and troubleshooting.

Example

No code snippet is provided as the issue is related to configuration and plugin management.

Notes

The encrypted log files and lack of detailed error messages make it challenging to provide a more specific solution. The provided information suggests that addressing the stale plugin config entries and memory leaks may resolve the issues, but further investigation is required.

Recommendation

Apply a workaround by addressing the stale plugin config entries and monitoring the memory usage, as the root cause of the issue is likely related to the plugin configuration and memory management.

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

  1. CLI commands should exit with code 0 on success. Config warnings (stale plugin entries) should not cause non-zero exit codes.
  2. WeChat message delivery should succeed reliably.
  3. Crashpad crash dumps should be uploaded to the remote crash server automatically.
#training loop#device allocation#model download#tokenizer error#memory leak

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]: Windows QClaw gateway exit code 1, WebSocket message delivery failure, crash dumps not uploaded [2 comments, 3 participants]