You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm I don't think anything should've changed in this department, what model are you using?
We did include reasoning by default for gpt-5 and that will make thinking blocks render but Idk if that'd be the issue here since I imagine that'd be eating cpu rather than ram i dont see anything else in recent release affecting it.
Dax has been working on rewriting the tui and it should address a whole bunch of performance issues
Hmm I don't think anything should've changed in this department, what model are you using?
We did include reasoning by default for gpt-5 and that will make thinking blocks render but Idk if that'd be the issue here i dont see anything else in recent release affecting it.
Dax has been working on rewriting the tui and it should address a whole bunch of performance issues
Update: I tried rolling back to v0.11.7 and noticed that Bun's RAM usage is much lower compared to v0.11.8. On v0.11.8, Bun's memory usage keeps increasing and can reach almost 4GB even on moderate usage, but in v0.11.7, RAM usage stays well below 600MB. This suggests the recent update introduced a significant memory regression.
also experiencing this on my m1 mac (using sonnet 4.5 model from anthropic)
if i notice, the memory high usage will occured if opencode trying to read file(s), (start with permission to read),
after it read all of my file, the memory gone up and even if it already done reading, the memory still didnt go down.
So, what i do was to quit session and then start opencode again using /session
hmm, interesting @rekram1-node
as per 0.15.3 version, i try to re-create the situation, the memory still okay,
will let you know if something happened ever again.
thanks
I just had the same problem! I have 64GB of RAM, and out of nowhere, Bun started using 40GB of RAM. That's a big problem with Bun. I did some research, and there are issues with Bun related to this.
Reacted by daipham3198, Alessandro Mancini, Ahmed Benyahia and Tomislav Balaz
Activity
github-actions commentedon Sep 26, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
rekram1-node commentedon Sep 26, 2025
Hmm I don't think anything should've changed in this department, what model are you using?
We did include reasoning by default for gpt-5 and that will make thinking blocks render but Idk if that'd be the issue here since I imagine that'd be eating cpu rather than ram i dont see anything else in recent release affecting it.
Dax has been working on rewriting the tui and it should address a whole bunch of performance issues
iyang1016 commentedon Sep 26, 2025
hello sir, I use Z.ai: glm-4.5( Coding Plan)
iyang1016 commentedon Sep 26, 2025
Update: I tried rolling back to v0.11.7 and noticed that Bun's RAM usage is much lower compared to v0.11.8. On v0.11.8, Bun's memory usage keeps increasing and can reach almost 4GB even on moderate usage, but in v0.11.7, RAM usage stays well below 600MB. This suggests the recent update introduced a significant memory regression.
rekram1-node commentedon Sep 26, 2025
interesting well thx for looking at it ill take a look
edwarbudiman commentedon Oct 7, 2025
also experiencing this on my m1 mac (using sonnet 4.5 model from anthropic)
if i notice, the memory high usage will occured if opencode trying to read file(s), (start with permission to read),
after it read all of my file, the memory gone up and even if it already done reading, the memory still didnt go down.
So, what i do was to quit session and then start opencode again using /session
rekram1-node commentedon Oct 7, 2025
@edwarbudiman could be the lsp servers, what kinda project is it? You can disable them if u need to
lsp: {
serverId: {
disabled: true
}
}
for full list of servers see here: https://opencode.ai/docs/lsp/#built-in
edwarbudiman commentedon Oct 15, 2025
hmm, interesting @rekram1-node
as per 0.15.3 version, i try to re-create the situation, the memory still okay,
will let you know if something happened ever again.
thanks
rekram1-node commentedon Oct 15, 2025
sounds good!
dhruvkej9 commentedon Dec 31, 2025
@rekram1-node @thdxr Still the memory usage is very high I am using "1.0.218" version of opencode and the RAM opencode consumes is very high.
When can we expect it to be fixed, as it remains a critical blocker and opencode crashes after sometime
I just have playwright MCP enabled for debugging
rekram1-node commentedon Dec 31, 2025
@dhruvkej9 can u provide steps to reproduce? Can u provide a session that causes it?
aniel300 commentedon Jan 22, 2026
why is it doing this form time to time, will it recover?
JoakuGit commentedon Feb 1, 2026
+1
I just had the same problem! I have 64GB of RAM, and out of nowhere, Bun started using 40GB of RAM. That's a big problem with Bun. I did some research, and there are issues with Bun related to this.
github-actions commentedon Apr 2, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
jemag commentedon Apr 2, 2026
should have been marked as stale first, this doesn't leave the opportunity to keep the issue open when it is still relevant (which is the case)