Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Claude Desktop v1.3109.0 crashes on launch (V8 OOM) — macOS 26.5 beta [2 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#49579•Fetched 2026-04-17 08:37:08
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
joereg4joereg4
Participants
github-actions[bot]github-actions[bot]joereg4joereg4
Timeline (top)
labeled ×4commented ×2closed ×1

Error Message

(node:23687) [DEP0040] DeprecationWarning: The punycode module is deprecated. (node:23687) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 change listeners added to [RAr]. MaxListeners is 10.

Error occurred in handler for '$eipc_message$_...claude.buddy$BuddyBleTransport$_reportState': Error: No handler registered for '...BuddyBleTransport$_reportState'

<--- Last few GCs ---> [23687:0x10400500000] 5940 ms: Mark-Compact (reduce) 3180.0 (3299.0) -> 3180.0 (3217.3) MB, pooled: 0.0 MB, 13.28 / 0.00 ms (average mu = 0.562, current mu = 0.322) last resort; GC in old space requested [23687:0x10400500000] 5954 ms: Mark-Compact (reduce) 3180.0 (3217.3) -> 3180.0 (3207.8) MB, pooled: 0.0 MB, 13.66 / 0.00 ms (average mu = 0.381, current mu = 0.001) last resort; GC in old space requested

[23687:0416/174420.707885:ERROR:electron/shell/common/node_bindings.cc:185] OOM error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Code Example

(node:23687) [DEP0040] DeprecationWarning: The `punycode` module is deprecated.
(node:23687) MaxListenersExceededWarning: Possible EventEmitter memory leak detected.
  11 change listeners added to [RAr]. MaxListeners is 10.

Error occurred in handler for '$eipc_message$_..._claude.buddy_$_BuddyBleTransport_$_reportState':
  Error: No handler registered for '..._BuddyBleTransport_$_reportState'

<--- Last few GCs --->
[23687:0x10400500000]  5940 ms: Mark-Compact (reduce) 3180.0 (3299.0) -> 3180.0 (3217.3) MB,
  pooled: 0.0 MB, 13.28 / 0.00 ms (average mu = 0.562, current mu = 0.322) last resort;
  GC in old space requested
[23687:0x10400500000]  5954 ms: Mark-Compact (reduce) 3180.0 (3217.3) -> 3180.0 (3207.8) MB,
  pooled: 0.0 MB, 13.66 / 0.00 ms (average mu = 0.381, current mu = 0.001) last resort;
  GC in old space requested

[23687:0416/174420.707885:ERROR:electron/shell/common/node_bindings.cc:185]
  OOM error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

<h2>Environment</h2>
DetailValue
App version1.3109.0
macOS26.5 beta (Build 25F5042g)
HardwareMac Mini, Apple Silicon M2, 24 GB RAM
<h2>Description</h2> <p>Claude Desktop crashes with a V8 out-of-memory error every time the app launches Code mode. Regular chat mode works fine. The crash occurs within ~8-12 seconds of the VM initializing, consistently hitting ~3.2-3.3 GB of V8 heap before dying.</p> <p>This is a <strong>fully clean install</strong> — all app data, caches, MCP servers, IndexedDB, and vm_bundles were deleted before reproducing. The crash occurs with zero configuration.</p> <h2>Additional Observations</h2> <ul> <li><strong>Regular chat mode works</strong> — the app is stable as long as Code/Cowork is not activated</li> <li><strong><code>NODE_OPTIONS="--max-old-space-size=6144"</code> has no effect</strong> — Electron appears to ignore the flag; heap still caps at ~3.2 GB</li> <li><strong><code>BuddyBleTransport</code> errors fire on every launch</strong> regardless of crash, possibly a Bluetooth companion feature incompatible with macOS 26.5 beta APIs</li> <li><strong><code>MaxListenersExceededWarning</code></strong> appears on every launch — potential EventEmitter memory leak contributing to the OOM</li> <li><strong>IndexedDB LevelDB lock errors</strong> also appear on launch (<code>LOCK: File currently in use</code>) but are non-fatal</li> <li><strong>vm_bundles had ballooned to 7.9 GB</strong> on the previous install before cleanup; the fresh install begins rebuilding the VM bundle (<code>sessiondata.img created</code>) immediately before crashing</li> </ul> <h2>Troubleshooting Already Attempted</h2> <p>All of the following were tried with no improvement to Code/Cowork stability:</p> <ul> <li>Full app reinstall (twice — including deleting /Applications/Claude.app and redownloading)</li> <li>Deleted all caches: Cache/, Code Cache/, GPUCache/, DawnGraphiteCache/, DawnWebGPUCache/, Crashpad/</li> <li>Deleted vm_bundles/ (was 7.9 GB)</li> <li>Deleted IndexedDB and removed stale LOCK file</li> <li>Removed all MCP server configuration (claude_desktop_config.json set to empty mcpServers)</li> <li>Deleted Preferences, Saved Application State, WebKit, and Caches plist files</li> <li>Set <code>NODE_OPTIONS="--max-old-space-size=6144"</code> before launch</li> <li>80%+ system memory free at time of crash</li> </ul> <h2>Related Issues</h2> <ul> <li>#48261 — V8 OOM / JavaScript heap out of memory (macOS 26.3.1, M5)</li> <li>#32170 — Claude Desktop crashing on opening (macOS 26.3, M4)</li> <li>#29625 — Crashes on launch (macOS 26.4 beta, M2)</li> <li>#26646 — Freezing, API 500 errors, 12GB VM bundle (macOS 26.3)</li> </ul>

What Should Happen?

<p>Code and Cowork modes should launch without exhausting the V8 heap.</p></body></html>

Error Messages/Logs

(node:23687) [DEP0040] DeprecationWarning: The `punycode` module is deprecated.
(node:23687) MaxListenersExceededWarning: Possible EventEmitter memory leak detected.
  11 change listeners added to [RAr]. MaxListeners is 10.

Error occurred in handler for '$eipc_message$_..._claude.buddy_$_BuddyBleTransport_$_reportState':
  Error: No handler registered for '..._BuddyBleTransport_$_reportState'

<--- Last few GCs --->
[23687:0x10400500000]  5940 ms: Mark-Compact (reduce) 3180.0 (3299.0) -> 3180.0 (3217.3) MB,
  pooled: 0.0 MB, 13.28 / 0.00 ms (average mu = 0.562, current mu = 0.322) last resort;
  GC in old space requested
[23687:0x10400500000]  5954 ms: Mark-Compact (reduce) 3180.0 (3217.3) -> 3180.0 (3207.8) MB,
  pooled: 0.0 MB, 13.66 / 0.00 ms (average mu = 0.381, current mu = 0.001) last resort;
  GC in old space requested

[23687:0416/174420.707885:ERROR:electron/shell/common/node_bindings.cc:185]
  OOM error in V8: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Steps to Reproduce

<ol> <li>Fresh install of Claude Desktop 1.3109.0 from claude.ai/download</li> <li>Delete all app data: <pre><code>rm -rf ~/Library/Application\ Support/Clauderm -rf ~/Library/Caches/com.anthropic.claudefordesktop*rm -rf ~/Library/Preferences/com.anthropic.claudefordesktop* </code></pre></li> <li>Launch from Terminal: <code>/Applications/Claude.app/Contents/MacOS/Claude</code></li> <li>Regular chat loads successfully</li> <li>Navigate to Code or Cowork → crash within seconds</li> </ol>

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

v1.3109.0

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely caused by a memory leak or excessive memory allocation in the Claude Desktop application, leading to a V8 out-of-memory error when launching Code or Cowork modes.

Guidance

  • Investigate the MaxListenersExceededWarning and potential EventEmitter memory leak, as it may be contributing to the out-of-memory error.
  • Review the BuddyBleTransport errors and their potential impact on memory usage, considering the incompatibility with macOS 26.5 beta APIs.
  • Examine the vm_bundles rebuild process and its memory requirements, given that the previous install had a 7.9 GB vm_bundles directory.
  • Consider the relationship between the LOCK: File currently in use IndexedDB errors and the out-of-memory error, although they are reported as non-fatal.

Example

No specific code snippet can be provided without further information on the application's codebase. However, reviewing the error logs and troubleshooting steps may help identify the root cause of the memory leak or excessive allocation.

Notes

The issue may be related to previous reports (#48261, #32170, #29625, #26646), and investigating these issues may provide valuable insights. The fact that regular chat mode works fine suggests that the issue is specific to Code or Cowork modes.

Recommendation

Apply a workaround by investigating and addressing the potential memory leak or excessive allocation, as the root cause is not immediately clear. This may involve reviewing the application's code, adjusting configuration settings, or optimizing memory usage.

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…
#api#autograd error#model save/load#optimization#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