Memory leak

[yantianqi1]

Description

Logically speaking, a 16GB Mac shouldn't have its memory randomly wiped out. It shouldn't be happening all the time.
Error: Unknown error
ud@tauri://localhost/assets/index-D9T6R7qf.js:2:11977
@tauri://localhost/assets/index-D9T6R7qf.js:2:4664

────────────────────────────────────────
Caused by:
{}

Plugins

oo-my-opencode

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

[taxilian]

This ticket is very light on details, but I can confirm I've been seeing issues with memory growing out of bounds quite a bit myself.

I often run opencode in a coder workspace running on my kubernetes cluster; if the pod allocates more memory than is available it will be killed. I currently have that pod set to 32GB of ram because 16GB always got killed and it still eventually gets there.

I'm not 100% sure where all the issues are, but here are my thoughts / observations:

• Since node.js itself has a maximum amount of memory in a single process, it's probably related to some multi process things; not sure what those would be
• It seems to grow faster when subagents are used. If I had to guess, it seems like there are cases where subagents are no longer being used / have been essentially discarded but they aren't being cleaned up, so they just stay around forever or until you restart the process
• It seems like there are multiple things that don't get cleaned up because if I leave any opencode instance open for long enough it will eventually use enough memory to be a major issue.

[kov]

Could you give it a try with #9693 applied?

[rekram1-node]

Latest release also shipped some memory fixes

[censey]

testing with 1.1.27 and still massive memory consumption as it runs high models. I am actually noticing an increase in consumption rate using Opus high vs 1.1.25

[rekram1-node]

Probably just the same memory issue from before, no significant changes were made that could be increasing it and a dumb bug was fixed that definitely was causing at least some of it prior