openclaw - 💡(How to fix) Fix [Bug]: Comprehensive issues: CLI exit code 1, memory leak, crash dumps not uploaded, skill-interceptor auto-recovery [1 comments, 1 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#68815Fetched 2026-04-19 15:07:05
View on GitHub
Comments
1
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×2commented ×1

Multiple critical issues in QClaw 2026.3.13 on Windows: CLI returns exit code 1 on every command, 5 crash dumps (~33MB each) not uploaded for 2 weeks, memory leak ~1.5GB, and skill-interceptor auto-reenables after every update blocking 17 commonly-used skills.

Root Cause

Multiple critical issues in QClaw 2026.3.13 on Windows: CLI returns exit code 1 on every command, 5 crash dumps (~33MB each) not uploaded for 2 weeks, memory leak ~1.5GB, and skill-interceptor auto-reenables after every update blocking 17 commonly-used skills.

Fix Action

Fix / Workaround

  1. Install or upgrade to QClaw 2026.3.13 on Windows Server 2025 (10.0.26200 x64)
  2. Run any CLI command: openclaw status, openclaw cron list, openclaw gateway status
  3. Observe: all commands return exit code 1 even when gateway is functioning
  4. Check Crashpad reports directory: find 5 crash dump files (~33MB each) from 2026-03-28 to 2026-04-10, none uploaded
  5. Check memory: main QClaw process uses 1.5GB+ RAM
  6. Disable skill-interceptor plugin, then upgrade QClaw: plugin auto-reenables, blocking 17 skills again

Code Example

Config warnings on every CLI command:
- plugins.entries.imap-smtp-email: plugin not found (stale config)
- plugins.entries.memory-tencentdb: disabled but config present
- plugins.entries.openclaw-mem0: disabled but config present
- plugins.entries.skill-interceptor: disabled but config present

Gateway status: `Gateway unreachable (missing scope: operator.read)`

Crash dump files (all ~33MB, none uploaded):
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\29038b16-6873-41cf-af48-f5cff6af048c.dmp (2026-04-03)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\33a0bade-f1d2-4847-adca-75f4bb03a837.dmp (2026-04-10)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\4eead4cb-3b5b-4473-af9a-7b5e36761906.dmp (2026-03-28)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\8bee58a4-1887-41c1-98f8-e6cca57bbb3e.dmp (2026-04-02)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\f26305e7-c02c-44b8-b238-35db056c9c95.dmp (2026-04-04)

OpenClaw version: 2026.3.13 (61d171a), Node: 22.16.0
RAW_BUFFERClick to expand / collapse

Bug type

Crash (process/app exits or hangs)

Beta release blocker

No

Summary

Multiple critical issues in QClaw 2026.3.13 on Windows: CLI returns exit code 1 on every command, 5 crash dumps (~33MB each) not uploaded for 2 weeks, memory leak ~1.5GB, and skill-interceptor auto-reenables after every update blocking 17 commonly-used skills.

Steps to reproduce

  1. Install or upgrade to QClaw 2026.3.13 on Windows Server 2025 (10.0.26200 x64)
  2. Run any CLI command: openclaw status, openclaw cron list, openclaw gateway status
  3. Observe: all commands return exit code 1 even when gateway is functioning
  4. Check Crashpad reports directory: find 5 crash dump files (~33MB each) from 2026-03-28 to 2026-04-10, none uploaded
  5. Check memory: main QClaw process uses 1.5GB+ RAM
  6. Disable skill-interceptor plugin, then upgrade QClaw: plugin auto-reenables, blocking 17 skills again

Expected behavior

  1. CLI commands should return exit code 0 when gateway is functioning normally
  2. Crash dumps should be automatically uploaded to the server after each crash
  3. Memory usage should remain stable (not leak to 1.5GB+)
  4. skill-interceptor should stay disabled once user disables it; updates should not override user preferences

Actual behavior

  1. Every CLI command returns exit code 1 (exit code 0 expected)
  2. 5 Crashpad crash dumps (~33MB each) found locally; none uploaded to server:
    • 29038b16-6873-41cf-af48-f5cff6af048c.dmp — 2026-04-03
    • 33a0bade-f1d2-4847-adca-75f4bb03a837.dmp — 2026-04-10
    • 4eead4cb-3b5b-4473-af9a-7b5e36761906.dmp — 2026-03-28
    • 8bee58a4-1887-41c1-98f8-e6cca57bbb3e.dmp — 2026-04-02
    • f26305e7-c02c-44b8-b238-35db056c9c95.dmp — 2026-04-04
  3. Main QClaw process uses 1.5GB+ RAM (7 processes total ~1.7GB)
  4. WeChat message delivery fails intermittently ("This operation was aborted"), ~30% failure rate
  5. skill-interceptor auto-reenables after QClaw update; 17 skills blocked: tencent-docs, kdocs, notion, ima, youdaonote, weiyun, tencent-survey, tencent-meeting, imap-smtp-email, public-skill, all wecomcli plugins
  6. All log files are .enc encrypted; cannot read logs for diagnosis
  7. openclaw gateway restart causes Runtime: stopped; all CLI commands hang; only fix is kill gateway process

OpenClaw version

2026.3.13 (61d171a)

Operating system

Windows Server 2025 (10.0.26200 x64)

Install method

QClaw Windows installer

Model

qclaw/modelroute

Provider / routing chain

openclaw -> modelroute (qclaw/modelroute)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Config warnings on every CLI command:
- plugins.entries.imap-smtp-email: plugin not found (stale config)
- plugins.entries.memory-tencentdb: disabled but config present
- plugins.entries.openclaw-mem0: disabled but config present
- plugins.entries.skill-interceptor: disabled but config present

Gateway status: `Gateway unreachable (missing scope: operator.read)`

Crash dump files (all ~33MB, none uploaded):
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\29038b16-6873-41cf-af48-f5cff6af048c.dmp (2026-04-03)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\33a0bade-f1d2-4847-adca-75f4bb03a837.dmp (2026-04-10)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\4eead4cb-3b5b-4473-af9a-7b5e36761906.dmp (2026-03-28)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\8bee58a4-1887-41c1-98f8-e6cca57bbb3e.dmp (2026-04-02)
- C:\Users\Administrator\AppData\Roaming\QClaw\Crashpad\reports\f26305e7-c02c-44b8-b238-35db056c9c95.dmp (2026-04-04)

OpenClaw version: 2026.3.13 (61d171a), Node: 22.16.0

Impact and severity

Affected: Single-user QClaw installation on Windows Server 2025 Severity: Critical — CLI is broken (exit code 1 on all commands), crashes are not reported to developers, memory leak causes resource exhaustion Frequency: CLI exit code 1: always; Crash dumps not uploaded: every crash for 2 weeks; Memory leak: continuous; skill-interceptor auto-recovery: after every QClaw update Consequence: Developers receive no crash reports despite recurring crashes; CLI diagnostics are unreliable; user must manually fix skill-interceptor after every update; system memory pressure from 1.5GB+ per process

Additional information

Additional issues not listed above:

  • 4 stale plugin config entries remain after uninstall/disable: imap-smtp-email, memory-tencentdb, openclaw-mem0, skill-interceptor
  • Gateway restart causes Runtime failure (dangerous command on this system)
  • Gateway missing operator.read scope
  • WeChat channel requires periodic manual restarts to stay connected (last incident: 2026-04-17)
  • Log files are .enc encrypted; some log directories locked by SYSTEM account — both prevent diagnosis
  • Related issue: #68810 (submitted earlier today with additional diagnostic details)

extent analysis

TL;DR

The most likely fix involves addressing the configuration issues, such as removing stale plugin entries and ensuring the correct scope for the gateway, to resolve the CLI exit code 1 issue, crash dump uploads, and memory leak.

Guidance

  1. Remove stale plugin config entries: Delete the configuration files for imap-smtp-email, memory-tencentdb, openclaw-mem0, and skill-interceptor to prevent them from causing issues.
  2. Verify gateway scope: Ensure that the gateway has the necessary operator.read scope to function correctly.
  3. Investigate memory leak: Monitor the system's memory usage to identify the cause of the 1.5GB+ memory leak and take steps to mitigate it.
  4. Disable skill-interceptor permanently: Find a way to permanently disable the skill-interceptor plugin to prevent it from auto-re-enabling after updates.
  5. Check for related issues: Review the related issue #68810 for additional diagnostic details and potential solutions.

Example

No code snippet is provided as the issue is more related to configuration and system setup.

Notes

The encrypted log files and locked log directories may hinder diagnosis. It is essential to find a way to access these logs to gain more insight into the issues.

Recommendation

Apply a workaround by removing stale plugin entries, verifying the gateway scope, and investigating the memory leak. This should help mitigate some of the critical issues until a more permanent fix can be found.

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 return exit code 0 when gateway is functioning normally
  2. Crash dumps should be automatically uploaded to the server after each crash
  3. Memory usage should remain stable (not leak to 1.5GB+)
  4. skill-interceptor should stay disabled once user disables it; updates should not override user preferences

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]: Comprehensive issues: CLI exit code 1, memory leak, crash dumps not uploaded, skill-interceptor auto-recovery [1 comments, 1 participants]