2 people reported

All time, since Sep 25.

Large transcript crash-loops host

“The affected session can never be opened in the extension again.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/1529/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 2 a week at the late-September peak.

Opening large session transcripts crash-loops the VS Code extension host. Extension host runs out of memory parsing the whole transcript; restored tabs reload the session and crash it again.

Is this your bug?

File my report
Where
VS Code extension
Error text
Extension host terminated unexpectedly 3 times within the last 5 minutes
Versions
2.1.282 to 2.1.288
Platforms
Windows
How bad
Stops work: a core feature can't be used.

Not quite your bug?

  1. Orphan Claude processes left running4 people

Original reports3, newest first

  1. VS Code: opening a session whose transcript exceeds 2 GiB crash-loops the extension host#99088
  2. VS Code: post-compact skip ignored when boundaries carry preservedSegment — every tab parses the whole transcript, tab restore after host restart OOM-loops (2.1.282)#97230
  3. VS Code: transcript >2 GiB causes infinite re-parse loop, extension host OOM kills all Claude tabs (2.1.282)#97229

Do you work on Claude Code?

Claim its RAP Sheet to see what your users report and answer them in one place.