[FEATURE]: TUI whole and LSP memory limits as part of configuration #6521

Open
opened 2026-02-16 18:04:27 -05:00 by yindo · 1 comment
Owner

Originally created by @adiled on GitHub (Jan 16, 2026).

Originally assigned to: @rekram1-node on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

For a while the TUI has been leaking memory and perhaps LSPs are adding to the share, while several of these issues are still open, it would be nice to have memory restrained via opencode config.

If we don't: You have to wrap the cli call or do weird gymnastic to contain the process, and that takes the charm away of simply opencodeing your way into TUI.

Originally created by @adiled on GitHub (Jan 16, 2026). Originally assigned to: @rekram1-node on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request For a while the TUI has been leaking memory and perhaps LSPs are adding to the share, while several of these issues are still open, it would be nice to have memory restrained via opencode config. **If we don't:** You have to wrap the cli call or do weird gymnastic to contain the process, and that takes the charm away of simply `opencode`ing your way into TUI.
yindo added the discussionperf labels 2026-02-16 18:04:27 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 16, 2026):

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

  • #3013: Uses a huge amount of memory - Memory growth during extensive AI session usage
  • #2805: High RAM usage in latest release - Post-Bun runtime memory concerns
  • #7261: v1.1.6 still has memory bloat - Detailed analysis of Go heap arena accumulation and MCP orphan processes
  • #5363: opencode eating 70gb of memory - Memory consumption reaching extreme levels
  • #3995: Single opencode session is consuming 23+GB of memory - Extreme memory usage in single session
  • #7046: memory leak - General memory leak reports

These issues document the underlying memory problems affecting the TUI and LSP. Your feature request for memory limit configuration would help contain these issues until the root causes are fixed.

Feel free to ignore if your specific case differs from these.

@github-actions[bot] commented on GitHub (Jan 16, 2026): This issue might be a duplicate of existing issues. Please check: - #3013: Uses a huge amount of memory - Memory growth during extensive AI session usage - #2805: High RAM usage in latest release - Post-Bun runtime memory concerns - #7261: v1.1.6 still has memory bloat - Detailed analysis of Go heap arena accumulation and MCP orphan processes - #5363: opencode eating 70gb of memory - Memory consumption reaching extreme levels - #3995: Single opencode session is consuming 23+GB of memory - Extreme memory usage in single session - #7046: memory leak - General memory leak reports These issues document the underlying memory problems affecting the TUI and LSP. Your feature request for memory limit configuration would help contain these issues until the root causes are fixed. Feel free to ignore if your specific case differs from these.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6521