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

Open
opened 2026-02-16 18:12:27 -05:00 by yindo · 1 comment
Owner

Originally created by @CorrM on GitHub (Feb 15, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

  • Just starting OpenCode without doing anything, and it starts eating my RAM (+17 GB)!.
  • Just starting OpenCode spawn a git processes that eat my 24-thread CPU at 100% usage!.
  • Open any old session and keep spawn multi git processes.
  • For some reason it starts a LOT of rustc processes while it is literally not doing anything, just opening an old session! Yes, it's not coming from neovim or vscode. comes from opencode.

One more thing, even if I close the terminal, opencode and git processes are still alive! Killing them manually is necessary!

Yes, it's 1 Frame per minute TUI

Plugins

"opencode-gemini-auth@latest", "opencode-websearch-cited@latest", "@franlol/opencode-md-table-formatter@latest", "@nick-vi/opencode-type-inject", "opencode-antigravity-auth@latest", "oh-my-opencode"

OpenCode version

1.2.5

Steps to reproduce

No response

Screenshot and/or share link

Image Image Image Image

Operating System

Arch Linux btw

Terminal

Kitty

Originally created by @CorrM on GitHub (Feb 15, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description - Just starting `OpenCode` without doing anything, and it starts eating my RAM (+17 GB)!. - Just starting `OpenCode` spawn a `git` processes that eat my 24-thread CPU at 100% usage!. - Open any old session and keep spawn multi `git` processes. - For some reason it starts a LOT of `rustc` processes while it is literally not doing anything, just opening an old session! Yes, it's not coming from `neovim` or `vscode`. comes from `opencode`. One more thing, even if I close the terminal, opencode and git processes are still alive! Killing them manually is necessary! _Yes, it's 1 Frame per minute TUI_ ### Plugins "opencode-gemini-auth@latest", "opencode-websearch-cited@latest", "@franlol/opencode-md-table-formatter@latest", "@nick-vi/opencode-type-inject", "opencode-antigravity-auth@latest", "oh-my-opencode" ### OpenCode version 1.2.5 ### Steps to reproduce _No response_ ### Screenshot and/or share link <img width="1679" height="242" alt="Image" src="https://github.com/user-attachments/assets/2c3df8b8-4e93-461e-ac1a-ff6443d47124" /> <img width="1671" height="242" alt="Image" src="https://github.com/user-attachments/assets/9fc96d35-5b53-4a49-9855-5b978b678cc6" /> <img width="1673" height="120" alt="Image" src="https://github.com/user-attachments/assets/fb97cd2c-9d39-4bf7-84a7-c9999a9c51d1" /> <img width="1720" height="962" alt="Image" src="https://github.com/user-attachments/assets/379e266c-d44f-4088-8a54-bcc1ff221a8e" /> ### Operating System Arch Linux btw ### Terminal Kitty
yindo added the bugperf labels 2026-02-16 18:12:27 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 15, 2026):

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

Potential Duplicates:

  • #13230: [Critical] Memory leak causes kernel soft lockups (356s, 7/8 CPUs), OOM kills (111GB virt/21GB RSS), and total system death on Linux
  • #13513: [Performance] Critical CPU usage and memory leak even when starting a new session
  • #13041: Per-session MCP server and LSP duplication multiplies memory usage across concurrent sessions
  • #13328: [Bug] LSP freezes and diagnostics timeout too short (3s) for heavy language servers
  • #12913: Opencode processes survive terminal disconnect, become orphans, and leak memory
  • #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:

  • #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).

@github-actions[bot] commented on GitHub (Feb 15, 2026): This issue appears to be a duplicate of existing critical memory and performance issues that the team is actively working on: **Potential Duplicates:** - #13230: [Critical] Memory leak causes kernel soft lockups (356s, 7/8 CPUs), OOM kills (111GB virt/21GB RSS), and total system death on Linux - #13513: [Performance] Critical CPU usage and memory leak even when starting a new session - #13041: Per-session MCP server and LSP duplication multiplies memory usage across concurrent sessions - #13328: [Bug] LSP freezes and diagnostics timeout too short (3s) for heavy language servers - #12913: Opencode processes survive terminal disconnect, become orphans, and leak memory - #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:** - #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).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#9443