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
{{ message }}
Repository navigation
[Performance] Critical CPU usage and memory leak even when starting a new session #12513
The application becomes extremely sluggish immediately after startup. Even with a fresh session and no large files open, the system becomes nearly unresponsive.
Diagnostic Observations
Monitoring via top reveals critical resource consumption:
CPU Usage: Consistently hitting nearly 200%.
Virtual Memory: The process is requesting approximately 92.5GB, which is abnormal for a fresh session.
Steps to Reproduce:
Plugins
oh-my-opencode
OpenCode version
1.1.53
Steps to reproduce
Launch Opencode
Create or open a new session (with no large projects/files).
Wait for 30–60 seconds.
Check system resources via top or htop
Expected Behavior
The application should idle at a reasonable CPU and memory footprint when no heavy tasks are being performed
I’ve done some further investigation into the 100% CPU usage. It appears that Opencode is pinning a single CPU core to 100% while other cores remain idle or underutilized.
I'm experiencing this too, and also very high memory usage (3.5gb on startup, and climbs). I don't have Oh-My-Opencode, but do have osgrep and some other plugins/mcps. Is there a way to inspect this to pinpoint?
I'm experiencing this too, and also very high memory usage (3.5gb on startup, and climbs). I don't have Oh-My-Opencode, but do have osgrep and some other plugins/mcps. Is there a way to inspect this to pinpoint?
Same problem here with MacBook Air M1 on MacOS 26.2
Activity
github-actions commentedon Feb 6, 2026
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
roymecat commentedon Feb 6, 2026
I’ve done some further investigation into the 100% CPU usage. It appears that Opencode is pinning a single CPU core to 100% while other cores remain idle or underutilized.
cloudpresser commentedon Feb 14, 2026
I'm experiencing this too, and also very high memory usage (3.5gb on startup, and climbs). I don't have Oh-My-Opencode, but do have osgrep and some other plugins/mcps. Is there a way to inspect this to pinpoint?
felipecarvalho commentedon Feb 14, 2026
Same problem here with MacBook Air M1 on MacOS 26.2
thdxr commentedon Apr 2, 2026
Closing in favor of #20695 where we're collecting all memory-related problems. Please follow that issue for updates.
Merge pull request #2 from herjarsa/fix/sqlite-wal-crash-on-open-24287