Memory Leak - Commit Size Exceeds 70GB

[ayaka209]

Description

The application experiences a critical memory leak where the commit size (reserved memory) grows continuously and indefinitely during use. The commit size can exceed 70GB without ever being released, eventually exhausting all available system memory (physical RAM + page file) and causing system instability or crashes.

Plugins

Oh-My-OpenCode

OpenCode version

1.1.65

Steps to reproduce

1. Open a Rust project with LSP (Language Server Protocol) enabled
2. Use Claude Opus model with Sisyphus agent
3. Engage in extended conversations with multiple interactions
4. Monitor memory usage in Task Manager (Details tab → Commit size column)

Screenshot and/or share link

Working Set and Commit Size

Operating System

Win11 Pro 25H2 26200.7840

Terminal

Windows Terminal

[github-actions]

---

This issue appears to be a duplicate or closely related to existing memory leak reports. Please check:

• Serious memory leak on the Windows platform #10248: Serious memory leak on the Windows platform (12GB RAM consumption observed)
• Slow down the PC after hours usage and occupy large memory #12499: Slow down the PC after hours usage and occupy large memory (Windows, 53% RAM usage)
• [Performance] Critical CPU usage and memory leak even when starting a new session #12513: Critical CPU usage and memory leak even when starting a new session (92.5GB virtual memory)
• [BUG/PERF] Severe Memory Leak and Disk Swell leading to System Kernel Panic (macOS) #12687: Severe Memory Leak and Disk Swell leading to System Kernel Panic (macOS, 50GB disk swell)
• [Critical] Memory leak causes kernel soft lockups (356s, 7/8 CPUs), OOM kills (111GB virt/21GB RSS), and total system death on Linux #13230: Critical memory leak causes kernel soft lockups and OOM kills (111GB virtual / 21GB RSS on Linux)
• Per-session MCP server and LSP duplication multiplies memory usage across concurrent sessions #13041: Per-session MCP server and LSP duplication multiplies memory usage across concurrent sessions

Many of these issues share the same core symptoms you're reporting (unbounded memory growth, high commit size/virtual memory, Windows platform). These existing issues contain detailed technical investigation and proposed fixes that may be relevant to your case.

[ayaka209]

seems 1.2.0 fixed