[BUG] [Windows] 1.2773.0 browser-process V8 OOM on launch
Resolved 💬 2 comments Opened Apr 16, 2026 by akeemjones Closed May 25, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Claude Desktop 1.2773.0 closes on launch in Windows even after clean reinstall and a near-empty profile reset.
What Should Happen?
Claude should stay open normally and reach the home screen/login state instead of closing.
Error Messages/Logs
Crashpad dump signature:
- process_type = browser
- Electron 41.2.0
- electron.v8-oom.location = CALL_AND_RETRY_LAST
- electron.v8-oom.is_heap_oom
- OOM error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
main.log also shows:
- UnknownError: Internal error opening backing store for indexedDB.open
cowork-service.log still shows the app connects, signature-verifies, then drops with EOF shortly after. The VM service stays healthy.
I also tested with:
- VM bundle compression fixed/uncompressed
- transcript/session caches moved aside
- Chromium caches cleared
- broad Claude profile reset, leaving only claude_desktop_config.json and config.json
- CoworkVMService running normally
The crash still happens from that near-empty state.
Steps to Reproduce
- Install Claude Desktop 1.2773.0 on Windows.
- Launch Claude from Start.
- Wait for startup.
- Observe that the app closes within seconds, even after a clean reinstall and profile reset.
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.2773.0 (884b37) 2026-04-15T14:32:09.000Z
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
This is on Windows with an MSIX install (Claude_pzs8sxrjxfjjc). I already ruled out local profile bloat, transcript caches, VM bundle compression, and CoworkVMService instability. The browser-process dump still shows a V8 OOM signature after those resets.
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗