Memory leak: RSS grows to ~6 GB on ARM64 in 2.1.121 (regression similar to #28763)

Summary

Same memory leak pattern as #28763 has reappeared in 2.1.121. The claude process grows unbounded and is killed by the OOM killer within 30–60 minutes of an active session. #28763 was reported fixed in 2.1.58 — this is a fresh regression on a later version.

Environment

• Claude Code: 2.1.121
• Node: v20.19.2
• npm: 9.2.0
• OS: Debian 13 (trixie), Linux 6.12.75+rpt-rpi-2712
• Arch: aarch64 (Raspberry Pi 5, 8 GB RAM, 2 GB swap)
• Model: claude-opus-4-7[1m] (Opus 4.7, 1M context tier)

Repro

Normal usage — read/edit files, multi-turn coding session on a small repo. Within ~30–60 minutes the OS kills the claude process. Restart, repeat, same outcome.

Evidence (dmesg, 5 consecutive OOM kills)

Out of memory: Killed process 3695213 (claude) total-vm:75207488kB, anon-rss:5914480kB
Out of memory: Killed process 3695820 (claude) total-vm:75207536kB, anon-rss:5912752kB
Out of memory: Killed process 3697675 (claude) total-vm:75174704kB, anon-rss:5908048kB
Out of memory: Killed process 3698554 (claude) total-vm:75207552kB, anon-rss:5952128kB
Out of memory: Killed process 3699091 (claude) total-vm:75240240kB, anon-rss:5942944kB

Every kill: virtual ~75 GB, RSS ~5.9 GB. RSS is consistent across runs which suggests the leak grows until the OOM-killer fires at roughly the same point relative to total system memory.

Notes

• Started after an auto-update yesterday — system had been stable on a prior version for weeks before this.
• ARM64-specific? Possibly — original issue had platform:wsl label, but the failure mode (unbounded heap growth → OOM) is identical.
• 1M-context tier may amplify it but probably not the root cause; growth pattern suggests an ArrayBuffer / heap accumulation that doesn't release.

References: #28763, #27421