Renderer repeatedly crashes with V8 "Reached heap limit" OOM, correlates with diff tab open/close

Description

The VS Code renderer process crashes repeatedly (reason: 'crashed', code: '5'), showing the "The window terminated unexpectedly" dialog. This happened 15 times in a single evening session (18:10-20:59, roughly every 10-20 minutes).

Inspecting the Crashpad .dmp files directly (via strings) shows the crash is a V8 JS heap OOM, not an OS-level kill:

v8-oom-location
Reached heap limit
Script OOM (Reached heap limit).

Checked across 4 independent crash dumps from the same session - all show the same signature. No corresponding kernel/runningboardd/jetsam/sandboxd kill messages appear in the unified log at the crash timestamps, and main.log only shows:

Extension host with pid <pid> exited with code: 0, signal: unknown.
CodeWindow: renderer process gone (reason: crashed, code: 5)

with nothing in the Claude Code extension host log (Claude VSCode.log) near the crash time - no errors/warnings logged before it happens.

Environment

• VS Code: 1.133.0 (Electron 42.8.0)
• Extension: anthropic.claude-code 2.1.234 (darwin-arm64), latest as of writing
• OS: macOS (Apple Silicon)

Suspected trigger

Based on usage pattern across multiple sessions, the crashes correlate with opening/closing diff view tabs produced by the extension (reviewing edits Claude makes). Suspect something in the diff webview or the associated JS objects isn't being released, causing the renderer's V8 heap to grow unbounded across a session until it hits the heap limit and crashes.

Steps to reproduce (best guess, not fully isolated)

1. Use Claude Code extension for an extended session, having it open/close several diff tabs for file edits.
2. After roughly 10-20 minutes of this, the renderer crashes with the heap-limit OOM above.

Crash timestamps (single session, 2026-08-18)

18:10, 18:53, 18:56, 19:00, 19:03, 19:07, 19:25, 19:31, 19:43, 19:46, 19:56, 20:34, 20:42, 20:51, 20:59

Ask

• Is there a known memory leak tied to the diff view / diff tab lifecycle?
• Any recommended workaround (e.g., a setting to reduce retained diff state, or limit concurrent diff webviews) short of restarting VS Code every ~15 minutes?

---
Screenshot of the crash dialog attached below (drag-and-dropped manually).