›_ Claude Code Issues
Claude Code Issues / Error strings / JavaScript heap out of memory / Page 2

JavaScript heap out of memory — page 2

V8 exhausted its heap and aborted the process.

142 issues · 4 open · 138 resolved (97%) · first seen Mar 5, 2025

First response · local

What to do now

Most likely: The local Claude Code process crashed while parsing or executing.

  1. Record the Claude Code version and the first stack frame before restarting.
  2. Try a fresh session with the same minimal input to distinguish corrupted state from a repeatable crash.
  3. Preserve logs and compare reports from the same version before downgrading.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 7 new reports in the last 90 days vs 23 in the 90 before — -70%. The open backlog peaked at 26 in 2025-10 and sits at 4 today.

0 7 13 20 26 2025-032025-092026-032026-08
2025-03 — First reports2025-06 — Most new reports (26)2025-10 — Peak backlog (26 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

32 of these reports name the Claude Code build they were running, spanning 24 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 4 days across 138 closures. Of the 138 closures with a recorded reason, 20% were closed as completed and 111 as not-planned or duplicate. The most recent completed fix landed in 2026-06.

Workarounds reported by the community

31 of these issues post a workaround someone says worked. The highest-engagement ones:

Recurring crashes: JavaScript Heap Out of Memory while 'thinking'
Temporary fix:
Found in the thread of #1421 · still open
[BUG] VS Code extension crashes with OOM error: conversation history accumulates to 700MB+ causing infinite crash loop
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) -
Found in the description of #8722 · resolved
[BUG] JavaScript heap exhaustion (OOM crash) during heavy Task tool/agent usage
…s there a maximum recommended number of agents per session? Workarounds Attempted - Starting fresh sessions frequently (helps but disruptive) - Sequential instead of parallel agent spawning (reduces peak memory) - Smalle…
Found in the description of #16470 · resolved
[BUG] JavaScript heap out of memory crash when running parallel Explore subagents
…I use: I'm gonna spam this a few places since it's a useful workaround for some of the bugs in this claude code version where peak memory consumption may be 10x larger than average.
Found in the thread of #19100 · resolved
[BUG] Desktop app crashes on launch with V8 heap OOM — single session .jsonl grew to 3.7 GB
…outlier files at 3.7 GB and 1.9 GB, everything else <25 MB) Workaround that fixed it: - Move the two oversized .jsonl files out of ~/.claude/projects/ - App now launches cleanly and session history is ~1.1 GB Attempted w…
Found in the description of #48210 · resolved

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 101–142

Ranked by community engagement (reactions weighted over comments).

Related aggregations

  1. AbortError: the operation was aborted

    2,101 issues

  2. SyntaxError: Unexpected token

    698 issues

  3. Killed: 9 (SIGKILL / OOM killer)

    339 issues

  4. Segmentation fault (SIGSEGV / SIGABRT)

    289 issues

  5. TypeError: Cannot read properties of undefined

    194 issues

  6. Unhandled promise rejection

    59 issues