Memory leak, LSP spam, 1 Frame per minute #13796

Activity

1. corrm

   added

   bugSomething isn't workingSomething isn't working

   on Feb 16, 2026
2. github-actions

   assigned

   rekram1-node

   on Feb 16, 2026
3. github-actions

   added

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Feb 16, 2026
4. github-actions commented on Feb 16, 2026

   

   github-actionsbot

   on Feb 16, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue appears to be a duplicate of existing critical memory and performance issues that the team is actively working on:

   Potential Duplicates:

   • [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 (356s, 7/8 CPUs), OOM kills (111GB virt/21GB RSS), and total system death on Linux
   • feat: add tui.no_terminal_padding_x config option #13513: [Performance] Critical CPU usage and memory leak even when starting a new session
   • 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
   • [Bug] LSP freezes and diagnostics timeout too short (3s) for heavy language servers #13328: [Bug] LSP freezes and diagnostics timeout too short (3s) for heavy language servers
   • Opencode processes survive terminal disconnect, become orphans, and leak memory #12913: Opencode processes survive terminal disconnect, become orphans, and leak memory
   • High CPU usage since 1.1.60 using Ghostty #13490: High CPU usage since 1.1.60 using Ghostty

   Your symptoms (RAM spike, git processes at 100% CPU, rustc processes spawning) are consistent with the cascading memory leak and child process management issues already documented in #13230 and #13513.

   Related Issue:

   • LSP server crashes permanently disable language features for the session #13785: LSP server crashes permanently disable language features (relevant to the LSP spam mentioned)

   The team is tracking these under the broader memory leak initiative. Consider subscribing to #13230 or #13513 for updates on the fixes (which include bounding child processes, implementing LSP diagnostics eviction, and addressing unbounded output buffers in the bash tool).
5. marcusquinn commented on Mar 6, 2026

   

   marcusquinn

   on Mar 6, 2026

   More actions

   The RAM consumption you're seeing (+17 GB just from starting opencode) is likely caused by bash-language-server's hardcoded --external-sources flag triggering unbounded ShellCheck memory growth. We observed the exact same pattern — individual shellcheck processes growing to 3-5 GB RSS, compounding across sessions.

   The upstream root cause fix has been merged: bash-lsp/bash-language-server#1376 adds a shellcheckExternalSources config option. Setting it to false omits --external-sources entirely.

   Immediate workaround — set this env var before running opencode:

   SHELLCHECK_EXTERNAL_SOURCES=false

   See #16269 for the full analysis. The git/rustc CPU issues you mention may be separate problems, but the RAM explosion is very likely this.

   👍React with 👍2Reacted by Islam Nofl and W.T. Chang
6. SHL0MS

   added a commit that references this issue on Mar 15, 2026

   fix: remove dead LSP clients to prevent unbounded memory growth

   ...

   4c4c6e1
7. thdxr commented on Apr 2, 2026

   

   thdxr

   on Apr 2, 2026

   Member

   More actions

   Closing in favor of #20695 where we're collecting all memory-related problems. Please follow that issue for updates.

   👍React with 👍1Reacted by Islam Nofl
8. thdxr

   closed this as completedon Apr 2, 2026