claude-code - 💡(How to fix) Fix [BUG] Windows v1.2773.0: silent Electron main-process death ~20min after launch during background event-log flush [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
anthropics/claude-code#49123Fetched 2026-04-17 08:50:15
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1

Error Message

Happy to share main.log, claude.ai-web.log, cowork_vm_node.log from %APPDATA%\Claude\logs\ on request — they're large and contain personal session content so I'd prefer to share via a private channel rather than attach publicly.

Fix Action

Fix / Workaround

  • Windows 11 Home 10.0.26200, 32GB RAM
  • Claude Desktop shell 1.2773.0 (Microsoft Store install, auto-updated from 1.2581.0 on 2026-04-15 23:17)
  • CCD binary 2.1.92 (the deliberate rollback Anthropic shipped with this shell, per #46767-adjacent rollback)
  • Default profile, MCP servers: Gmail, Calendar, gdrive, Vercel, qmd, scheduled-tasks, dispatch, Claude in Chrome, computer-use, PDF, mcp-registry
  • A long-lived dispatch session (cse_…) plus CCD scheduled tasks (heartbeat-check, qmd-reindex, auto-flush-recovery, etc.)

Code Example

08:51:40 [info] Starting app { appVersion: '1.2773.0', nodeVersion: '24.14.0' }
08:51:40 [info] [CCD] Initialized with version 2.1.92
09:07:25 Spawning new session for scheduled task heartbeat-check
09:08:10 [CCD CycleHealth] healthy cycle (44s, hadFirstResponse=true)
09:09:58 Spawning new session for scheduled task qmd-reindex
09:10:15 [CCD CycleHealth] healthy cycle (17s, hadFirstResponse=true)
09:10:28 [info] [EventLogging] Flushing 16 events
<<< log ends; file mtime = 09:10:28; no further entries >>>
RAW_BUFFERClick to expand / collapse

What's wrong

After updating to Desktop shell 1.2773.0 on Windows 11, the entire Claude Desktop process dies silently roughly 20 minutes after launch. No crash dialog, no Crashpad dump, no Sentry report — main.log simply stops mid-sentence. The Electron main process exits, not just a renderer or CCD child.

This appears distinct from the related crash reports #48522 / #48926 (UI-switch-triggered) and #48813 (gradual 1-2 hour kernel pool leak), though I'm seeing elevated non-paged pool too (see below).

Environment

  • Windows 11 Home 10.0.26200, 32GB RAM
  • Claude Desktop shell 1.2773.0 (Microsoft Store install, auto-updated from 1.2581.0 on 2026-04-15 23:17)
  • CCD binary 2.1.92 (the deliberate rollback Anthropic shipped with this shell, per #46767-adjacent rollback)
  • Default profile, MCP servers: Gmail, Calendar, gdrive, Vercel, qmd, scheduled-tasks, dispatch, Claude in Chrome, computer-use, PDF, mcp-registry
  • A long-lived dispatch session (cse_…) plus CCD scheduled tasks (heartbeat-check, qmd-reindex, auto-flush-recovery, etc.)

Repro

  1. Launch Claude Desktop on Windows 11 (1.2773.0)
  2. Leave it idle / let CCD scheduled tasks run in background
  3. ~20 min later, the process dies silently. Task Manager shows no claude.exe; main.log ends mid-flush.

Crash signature (2026-04-16)

08:51:40 [info] Starting app { appVersion: '1.2773.0', nodeVersion: '24.14.0' }
08:51:40 [info] [CCD] Initialized with version 2.1.92
09:07:25 Spawning new session for scheduled task heartbeat-check
09:08:10 [CCD CycleHealth] healthy cycle (44s, hadFirstResponse=true)
09:09:58 Spawning new session for scheduled task qmd-reindex
09:10:15 [CCD CycleHealth] healthy cycle (17s, hadFirstResponse=true)
09:10:28 [info] [EventLogging] Flushing 16 events
<<< log ends; file mtime = 09:10:28; no further entries >>>

Both scheduled tasks completed cleanly. The process died 13 seconds after the last Stop hook, mid-event-flush. No exception, no graceful shutdown, no crash dump in %LOCALAPPDATA%\Claude\Crashpad\reports\.

Notes / related observations

  • Kernel non-paged pool at the time of writing (after ~2h of partial use): 1.04 GB (normal 0.2-0.5 GB). So #48813's leak is happening here too, but the sudden death at 20 min is too early to be the leak going terminal — looks like a separate failure mode.
  • Pre-update Desktop shell 1.2581.0 with the same CCD 2.1.92 was stable in the hours before the auto-update.
  • No Code/Chat tab switching took place — purely background activity. So this isn't #48522 / #48926.
  • [CCD] Ignoring defaultMode "bypassPermissions" from ~/.claude/settings.json warning visible — unrelated, but flagging in case it interacts with event-flush ordering.

Logs

Happy to share main.log, claude.ai-web.log, cowork_vm_node.log from %APPDATA%\Claude\logs\ on request — they're large and contain personal session content so I'd prefer to share via a private channel rather than attach publicly.

Related issues

  • #48522 — Claude Desktop Crashing (Windows, 1.2773.0, area:desktop)
  • #48926 — Application hang on Chat ↔ Code tab switch (Windows 11, 1.2773.0)
  • #48813 — Cowork/CC-in-Desktop ~19GB kernel non-paged pool leak (Windows)
  • #49023 — 1.2773.0 V8 OOM on launch (Windows)
  • #46767 — Tool results silently dropped (2.1.101 regression — clean on 2.1.92)

extent analysis

TL;DR

The issue can be mitigated by investigating and addressing the potential memory leak or resource exhaustion caused by the scheduled tasks and event flushing in the Claude Desktop application.

Guidance

  1. Investigate the scheduled tasks: Review the heartbeat-check and qmd-reindex tasks to ensure they are not causing excessive resource usage or memory leaks.
  2. Monitor event flushing: Examine the event flushing mechanism to determine if it is contributing to the application's sudden death, potentially due to resource exhaustion or other issues.
  3. Check for interactions with other components: Look into potential interactions between the CCD binary, Electron main process, and other components that might be contributing to the issue.
  4. Review system resources: Monitor system resources, such as memory and CPU usage, to identify any potential bottlenecks or leaks.
  5. Compare with previous versions: Since the issue appeared after updating to Desktop shell 1.2773.0, compare the behavior with the previous version (1.2581.0) to identify potential regressions.

Example

No specific code snippet can be provided without more information about the application's codebase. However, investigating the event flushing mechanism and scheduled tasks might involve reviewing code related to these components.

Notes

The issue might be related to the kernel non-paged pool leak mentioned in #48813, but the sudden death at 20 minutes suggests a separate failure mode. The [CCD] Ignoring defaultMode "bypassPermissions" from ~/.claude/settings.json warning should be investigated to rule out any potential interactions with the event-flush ordering.

Recommendation

Apply a workaround by investigating and addressing potential memory leaks or resource exhaustion caused by scheduled tasks and event flushing, as this is the most likely cause of the issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Windows v1.2773.0: silent Electron main-process death ~20min after launch during background event-log flush [1 comments, 2 participants]