Uses a huge amount of memory

When I use AI extensively in a session, opencode's memory usage will keep increasing until it gets stuck.

This issue might be a duplicate of existing issues. Please check:

High RAM usage in latest release #2805: High RAM usage in latest release - Reports unusually high memory consumption with Bun runtime after recent updates
Massive memory use on opening opencode when there is a very large file #2585: Massive memory use on opening opencode when there is a very large file - Reports 29GB RAM usage and slow computer performance, similar memory consumption pattern
Text rendering is VERY slow (and CPU usage is really high even when idle) #811: Text rendering is VERY slow (and CPU usage is really high even when idle) - Reports high CPU usage (25-30% when idle, 200-300% when active) along with performance issues
Absurd amount of cpu and memory usage when doing pah completion #496: Absurd amount of cpu and memory usage when doing path completion - Reports 100% CPU and memory usage, described as "like a forkbomb"
Critical Stability Issues: App Freezing & Hanging Analysis #731: Critical Stability Issues - Comprehensive analysis that includes memory-related stability issues and app freezing

Feel free to ignore if none of these address your specific case.

yeah current performance leaves a LOT to be desired, we are currently rewriting tui and it should be done this week most likely. It will have a lot of performance improvements.

Not sure if relevant to this issue, but one thing I have noticed is that when I run a debugger and either the server or the TUI stays paused on a breakpoint for a while, I would run out of memory on my system within a minute.

I'm guessing this might be because of messages queuing up and/or this code: https://github.com/sst/opencode/blob/c93c0d402d3130c6e69129395993ac1776132234/packages/opencode/src/server/tui.ts#L12

I'm also experiencing this with v0.15.3.

@dkmnx

@dkmnx what kind of project is it? Perhaps lsp servers are eating up the memory

@rekram1-node

@rekram1-node, its a rust project.

@dkmnx

@dkmnx is it fixed if you do:
opencode.json

{
"lsp": {
    "rust": {
      "disabled": true
    }
  },
}

Any updates here or suggestions from anyone? In my tiny neovim config directory I am getting large spikes in memory and cpu while streaming in chat responses. I am using WSL.

rewrite ships soon, hard to say what is causing your issue, maybe dry disabling the lua lsp?

{
"lsp": {
    "lua-ls": {
      "disabled": true
    }
  },
}

rewrite ships soon, hard to say what is causing your issue, maybe dry disabling the lua lsp?

Oh is it a full rewrite using opentui?

Yes, all the go code will be gone all the core logic stays.

@rekram1-node

@rekram1-node if I understand correctly, the rewrite is shipped with v1.0? I'm still experiencing debilitating memory usage caused by opencode starting a ton of lsp servers

hmm okay we will look into it...

Happy to test some things if you need in my free time. Otherwise, wish you luck.

limit the resources for opencode process
systemd-run --user --pty -p MemoryMax=8G -p CPUQuota=400% opencode
until they resolve the memory leak

@dkmnx is it fixed if you do: opencode.json
{
"lsp": {
    "rust": {
      "disabled": true
    }
  },
}

For me yes this resolves it. Otherwise it becomes an unmanageable amount of memory usage.

interesting...

interesting...

Claude Code with rust-analyser LSP enabled does not have the same issue, ghostty/nixos if that helps at all either.

their lsp serves different purposes and is only agent invoked afaik so im not surprised, but rust lsp is extremely memory hungry anytime I open rust projects in my ide it swallows a lot.

We should figure out how to mitigate this tho..

their lsp serves different purposes and is only agent invoked afaik so im not surprised, but rust lsp is extremely memory hungry anytime I open rust projects in my ide it swallows a lot.

We should figure out how to mitigate this tho..

ah okay understood. would be great to mitigate it, it's only an issue for me on RAM limited VMs as it quickly grows to eat up >16gb

Just here to mention I think I am having the same issue with my opencode version (1.1.51). I tried building with the following Fixes PR #11717 and PR #10914 still doesn't help. I am using an omarchy machine.

running into this too ):

I've noticed this too from the first time I tried it. I thought it's just my PC having issues. Now it's been two weeks and i am sure it's opencaude. I am running it in wsl. Honestly, it's very annoying as I have to kill my IDE and restart everything, It will also stop in the middle of the task

If you're running opencode in tmux on Linux, OOM kills are worse than you'd expect. The kernel doesn't just kill opencode. It killed my user systemd, which took tmux and my whole session with it.

I'm capping opencode with a systemd memory scope now. Alias in .zshrc / .bashrc:

# Memory-limit opencode so OOM kills don't take out your session
alias opencode="systemd-run --user --scope -p MemoryMax=8G -p MemorySwapMax=2G --description=opencode $HOME/.opencode/bin/opencode"

Set MemoryMax to whatever makes sense for your box (I'm on 16G, so 8G). The total ceiling is 10G (8G RAM + 2G swap). If opencode blows past the limit, the cgroup kills it and only it.

Note: if you run multiple opencode sessions, each gets its own 8G cap independently.

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

Navigation Menu

Repository navigation

Uses a huge amount of memory #3013

12 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Uses a huge amount of memory #3013

Description

Activity

github-actions commented on Oct 7, 2025

rekram1-node commented on Oct 7, 2025

veracioux commented on Oct 8, 2025

dkmnx commented on Oct 16, 2025

rekram1-node commented on Oct 16, 2025

dkmnx commented on Oct 16, 2025

rekram1-node commented on Oct 16, 2025

GitMurf commented on Oct 28, 2025

rekram1-node commented on Oct 28, 2025

GitMurf commented on Oct 28, 2025

rekram1-node commented on Oct 28, 2025

hmnd commented on Nov 13, 2025

12 remaining items

kanielrkirby commented on Nov 28, 2025

LautaroGScholtus commented on Jan 12, 2026

apekros commented on Jan 15, 2026

rekram1-node commented on Jan 15, 2026

apekros commented on Jan 15, 2026

rekram1-node commented on Jan 15, 2026

apekros commented on Jan 15, 2026

KaranjotVendal commented on Feb 4, 2026

broskees commented on Feb 7, 2026

AhmedBenyahia commented on Feb 15, 2026

sjdweb commented on Mar 12, 2026

thdxr commented on Apr 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions