Repository navigation
URGENT - "MEM LEAK", eats up gigabytes of ram until system crash #804
Description
immediately after starting up (AKA "opencode" in Linux CLI, nothing else, no command issued) the app spawns "gopls" threads, each with increasing mem footprint, eventually crashing the OS, requires spamming CTRL-C ("/exit" won't fully quit the app).
Metadata
Metadata
Assignees
Labels
No labels
Activity
mchzimm commentedon Jul 9, 2025
i re-installed go because i thought maybe that's the problem, but same issue
mchzimm commentedon Jul 9, 2025
so i started w/ v 0.2.6, because i remembered that one worked, then updated version-by-version. the "mem leak" issue starts with opencode v0.2.10, although it stabilizes after a few minutes and using up ~10gb, and cpu is going quite wild also:
this only got worse then going forward from v0.2.11 onward, and i had to spam CTRL-C to stop before it'd lock up the OS:
thdxr commentedon Jul 10, 2025
do you have a lot of
go.modfiles in your repo?mchzimm commentedon Jul 10, 2025
i'm not working on any go code, just python
mchzimm commentedon Jul 10, 2025
i upg to 0.2.18, the mem increase and high cpu util issues seem to be resolved.
still a lot of
goplsbut at with much less mem allocation and cpu utilization, and not keep spawning those repeatedly:so far so good!
mchzimm commentedon Jul 10, 2025
i'll close this issue for now, as it seems to be resolved
fix(commands): replace py_compile with compileall in build-fix (anoma…