Memory leak: ACP session event streams never aborted

[sauerdaniel]

Problem

In the ACP (Agent Communication Protocol) module, sessions and their event streams are not properly cleaned up:

1. Session Map Growth - Sessions are stored in a Map but never removed when completed
2. Event Stream Leaks - Event streams created via session.stream() are never aborted when sessions end
3. No Disposal Mechanism - No dispose() method exists to clean up session resources

Code Location

• packages/opencode/src/acp/agent.ts
• packages/opencode/src/acp/session.ts
• packages/opencode/src/acp/types.ts

Impact

• Memory grows with each session that completes
• Event stream listeners accumulate
• No way to explicitly clean up session resources

Relates to #5363

Expected Behavior

• Sessions should be removed from Map when completed
• Event streams should be aborted when session ends
• A dispose() method should be available for explicit cleanup

[github-actions]

This issue is part of a broader set of memory leak issues being tracked. While not direct duplicates, the following related issues address similar resource cleanup problems:

• ACP event subscription architecture causes cross-session pollution and duplicate events #5627: ACP event subscription architecture causes cross-session pollution and duplicate events
• Memory leak: Uncleaned timeouts, intervals, and subscriptions #9156: Memory leak: Uncleaned timeouts, intervals, and subscriptions
• Memory leak: TUI and Slack bot event listeners not cleaned up #9155: Memory leak: TUI and Slack bot event listeners not cleaned up
• Memory leak: MCP OAuth transports not closed on retry or cancellation #9153: Memory leak: MCP OAuth transports not closed on retry or cancellation
• opencode eating 70gb of memory? #5363: opencode eating 70gb of memory (general memory consumption issue)

These issues share the root cause of incomplete resource cleanup across different OpenCode modules. Consider reviewing all related memory leak issues together for a comprehensive cleanup strategy.