[Release] Uncontrolled Memory Growth Causing System Overload Due to Poor Resource Management #7214

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

Originally created by @StarMagicAI on GitHub (Jan 22, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

The official version of the open-source program suffers from continuous memory growth without effective release. Over time, this leads to system overload and crash. The root cause is identified as inadequate resource management mechanisms (e.g., unclosed handles, unreleased buffers) that fail to reclaim unused memory.

Originally created by @StarMagicAI on GitHub (Jan 22, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description The official version of the open-source program suffers from continuous memory growth without effective release. Over time, this leads to system overload and crash. The root cause is identified as inadequate resource management mechanisms (e.g., unclosed handles, unreleased buffers) that fail to reclaim unused memory.
yindo added the bugperf labels 2026-02-16 18:06:28 -05:00
Author
Owner

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

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

  • #9140: Memory leak: Unbounded caches grow without limit
  • #9156: Memory leak: Uncleaned timeouts, intervals, and subscriptions
  • #9157: Memory leak: Instance disposal doesn't clean up plugins or cached resources
  • #9154: Memory leak: ACP session event streams never aborted
  • #9155: Memory leak: TUI and Slack bot event listeners not cleaned up
  • #9153: Memory leak: MCP OAuth transports not closed on retry or cancellation

Feel free to ignore if this issue addresses a specific case not covered by those issues.

@github-actions[bot] commented on GitHub (Jan 22, 2026): This issue might be a duplicate of existing issues. Please check: - #9140: Memory leak: Unbounded caches grow without limit - #9156: Memory leak: Uncleaned timeouts, intervals, and subscriptions - #9157: Memory leak: Instance disposal doesn't clean up plugins or cached resources - #9154: Memory leak: ACP session event streams never aborted - #9155: Memory leak: TUI and Slack bot event listeners not cleaned up - #9153: Memory leak: MCP OAuth transports not closed on retry or cancellation Feel free to ignore if this issue addresses a specific case not covered by those issues.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7214