›_ Claude Code Issues
Claude Code Issues / Error strings / RangeError: Maximum call stack size exceeded

RangeError: Maximum call stack size exceeded

Unbounded recursion blew the JS stack.

30 issues · 1 open · 29 resolved (97%) · first seen May 2, 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 gone quiet. No new reports in the last 180 days — this looks resolved or superseded. The open backlog peaked at 11 in 2026-01 and sits at 1 today.

0 3 6 8 11 2025-052025-092026-012026-04
2025-05 — First reports2026-01 — Peak backlog (11 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

12 of these reports name the Claude Code build they were running, spanning 7 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 17 days across 29 closures. Of the 29 closures with a recorded reason, 21% were closed as completed and 23 as not-planned or duplicate. The most recent completed fix landed in 2026-01.

Workarounds reported by the community

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

[BUG] Stack overflow crash parsing ANSI-colored vitest output in v2.1.1
…through Claude Code Claude Code crashes with stack overflow Workaround: Running tests with NO COLOR=1 prevents the crash. Claude Code Version: 2.1.1 Platform: Claude Max Operating System: Linux (WSL) Terminal/Shell: (you…
Found in the description of #16786 · resolved
RangeError: Maximum call stack size exceeded in endOfWORD() - CLI crashes with long outputs
…experience for professional code analysis - Need for manual workarounds Current Workaround Instructing AI (via prompt engineering) to generate structured analysis instead of literal line-by-line citations, keeping output…
Found in the description of #9157 · resolved
RangeError: Maximum call stack size exceeded when running in tmux with large outputs
…gh scroll event rate ( 9935 reports 4,000-6,700 events/sec) Workarounds - Running Claude Code outside tmux (not ideal for workflows requiring multiple sessions) - Avoiding large outputs - Using wider tmux panes - Frequen…
Found in the description of #21529 · resolved
RangeError: Maximum call stack size exceeded in CZ function (v2.1.37)
…long conversations or multiple agents hit this frequently - Workaround: restart CLI, /compact, or increase Node stack size Attachments - Full error stack trace available - User context: nora-80b-runpod project, 30+ min c…
Found in the description of #25183 · resolved
[Bug] Stack Overflow in CLI v2.1.37 - Missing turnCount increment in CZ function
…long conversations or multiple agents hit this frequently - Workaround: restart CLI, /compact, or increase Node stack size Attachments - Full error stack trace available - User context: nora-80b-runpod project, 30+ min c…
Found in the description of #25182 · 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 1–30

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)

    337 issues

  4. Segmentation fault (SIGSEGV / SIGABRT)

    289 issues

  5. TypeError: Cannot read properties of undefined

    194 issues

  6. JavaScript heap out of memory

    142 issues