anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Critical Stability Issues: App Freezing & Hanging Analysis #531

New Issue
Closed
opened 2026-02-16 17:27:12 -05:00 by yindo · 5 comments
yindo commented 2026-02-16 17:27:12 -05:00
Owner
Copy Link
Copy Source

Originally created by @3dyuval on GitHub (Jul 6, 2025).

Originally assigned to: @thdxr on GitHub.

Problem Statement

Multiple critical stability issues are causing opencode to freeze or hang indefinitely, requiring external intervention to recover. Analysis of 8+ reported issues reveals systematic problems in process management, file handling, and external service integration.

Root Cause Categories

1. File System Bottlenecks

  • Large files (multi-GB .tar.gz) cause indefinite hangs
  • Synchronous file operations without size limits
  • Impact: Complete app freeze, "session is busy" errors

2. Process Management Gaps

  • Non-terminating processes make TUI unresponsive
  • Missing stdin handling causes sudo command deadlocks
  • Impact: ESC key ineffective, 1-minute timeout waits

3. MCP Server Failures ⚠️ Critical Missing Case

  • Failed MCP servers cause indefinite hangs during startup/operation
  • No timeout or health checks for MCP server connections
  • Impact: Complete app freeze when MCP servers fail to start or respond

4. Network/Firewall Conflicts

  • Hangs with network monitors (LuLu, Little Snitch)
  • No retry logic after firewall approval
  • Impact: Requires manual restart after network permission

5. Terminal Integration Issues

  • Scroll-related freezes, terminal corruption
  • Complex scroll debouncing logic causes instability
  • Impact: Complete terminal freeze, affects new sessions

Technical Evidence

Bash Tool Issues (packages/opencode/src/tool/bash.ts:30-38)

const process = Bun.spawn({
  cmd: ["bash", "-c", params.command],
  // Missing: stdin handling, process type detection, size limits
})

MCP Server Initialization (packages/opencode/src/mcp/index.ts:35-42)

const client = await experimental_createMCPClient({
  // ...
}).catch(() => {}) // Silent failure, no timeout

TUI Interrupt Handling (packages/tui/internal/tui/tui.go:256-272)

  • Complex debounce logic for interrupts
  • No direct process termination capability

Affected Issues

  • #519 - v0.1.161 hangs with no error messaging
  • #721 - Launching crashes file system (Linux)
  • #706 - Starting from source leads to freeze
  • #683 - Hangs with multi-GB .tar.gz files
  • #682 - TUI unresponsive with non-terminating processes
  • #652 - Unresponsive with sudo commands
  • #471 - Terminal freezes, can't open new sessions
  • #421 - Hangs with firewall/network monitors
  • #504 - Big mess in terminal when MCP server fails

Proposed Solutions

Phase 1: Critical Fixes (Immediate)

  1. File Size Guards - Add size validation before processing
  2. MCP Timeouts - Connection timeouts and health checks for MCP servers
  3. Command Detection - Identify interactive/long-running commands
  4. Process Interruption - Basic process termination capabilities

Phase 2: Architectural Improvements

  1. Streaming File Operations - Progressive loading with size limits
  2. Network Circuit Breakers - Retry logic and graceful degradation
  3. Resource Management - Memory/CPU limits and monitoring
  4. Error Boundaries - Component isolation and recovery

Success Criteria

  • ✅ Zero indefinite hangs on large files
  • ✅ Reliable process interruption with ESC key
  • ✅ Clean recovery from MCP server failures
  • ✅ Stable terminal behavior across platforms
  • ✅ Clear error messages when operations are blocked

Documentation

  • Branch: stability-analysis-issue
  • Full analysis: STABILITY_ANALYSIS.md
  • Architectural decisions: ARCHITECTURAL_DECISIONS.md
  • Implementation roadmap: 8 ADRs with phased approach

Priority: Critical - These issues make opencode unusable in common scenarios and require external intervention to recover.

Analysis based on issues #519, #721, #706, #683, #682, #652, #471, #421, #504 + comprehensive codebase review

Originally created by @3dyuval on GitHub (Jul 6, 2025). Originally assigned to: @thdxr on GitHub. ## Problem Statement Multiple critical stability issues are causing opencode to freeze or hang indefinitely, requiring external intervention to recover. Analysis of 8+ reported issues reveals systematic problems in process management, file handling, and external service integration. ## Root Cause Categories ### 1. **File System Bottlenecks** - Large files (multi-GB .tar.gz) cause indefinite hangs - Synchronous file operations without size limits - **Impact**: Complete app freeze, "session is busy" errors ### 2. **Process Management Gaps** - Non-terminating processes make TUI unresponsive - Missing stdin handling causes sudo command deadlocks - **Impact**: ESC key ineffective, 1-minute timeout waits ### 3. **MCP Server Failures** ⚠️ **Critical Missing Case** - Failed MCP servers cause indefinite hangs during startup/operation - No timeout or health checks for MCP server connections - **Impact**: Complete app freeze when MCP servers fail to start or respond ### 4. **Network/Firewall Conflicts** - Hangs with network monitors (LuLu, Little Snitch) - No retry logic after firewall approval - **Impact**: Requires manual restart after network permission ### 5. **Terminal Integration Issues** - Scroll-related freezes, terminal corruption - Complex scroll debouncing logic causes instability - **Impact**: Complete terminal freeze, affects new sessions ## Technical Evidence **Bash Tool Issues** (`packages/opencode/src/tool/bash.ts:30-38`) ```typescript const process = Bun.spawn({ cmd: ["bash", "-c", params.command], // Missing: stdin handling, process type detection, size limits }) ``` **MCP Server Initialization** (`packages/opencode/src/mcp/index.ts:35-42`) ```typescript const client = await experimental_createMCPClient({ // ... }).catch(() => {}) // Silent failure, no timeout ``` **TUI Interrupt Handling** (`packages/tui/internal/tui/tui.go:256-272`) - Complex debounce logic for interrupts - No direct process termination capability ## Affected Issues - #519 - v0.1.161 hangs with no error messaging - #721 - Launching crashes file system (Linux) - #706 - Starting from source leads to freeze - #683 - Hangs with multi-GB .tar.gz files - #682 - TUI unresponsive with non-terminating processes - #652 - Unresponsive with sudo commands - #471 - Terminal freezes, can't open new sessions - #421 - Hangs with firewall/network monitors - #504 - Big mess in terminal when MCP server fails ## Proposed Solutions ### Phase 1: Critical Fixes (Immediate) 1. **File Size Guards** - Add size validation before processing 2. **MCP Timeouts** - Connection timeouts and health checks for MCP servers 3. **Command Detection** - Identify interactive/long-running commands 4. **Process Interruption** - Basic process termination capabilities ### Phase 2: Architectural Improvements 1. **Streaming File Operations** - Progressive loading with size limits 2. **Network Circuit Breakers** - Retry logic and graceful degradation 3. **Resource Management** - Memory/CPU limits and monitoring 4. **Error Boundaries** - Component isolation and recovery ## Success Criteria - ✅ Zero indefinite hangs on large files - ✅ Reliable process interruption with ESC key - ✅ Clean recovery from MCP server failures - ✅ Stable terminal behavior across platforms - ✅ Clear error messages when operations are blocked ## Documentation - **Branch**: `stability-analysis-issue` - **Full analysis**: `STABILITY_ANALYSIS.md` - **Architectural decisions**: `ARCHITECTURAL_DECISIONS.md` - **Implementation roadmap**: 8 ADRs with phased approach **Priority**: Critical - These issues make opencode unusable in common scenarios and require external intervention to recover. --- *Analysis based on issues #519, #721, #706, #683, #682, #652, #471, #421, #504 + comprehensive codebase review*
yindo closed this issue 2026-02-16 17:27:12 -05:00
yindo commented 2026-02-16 17:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@RingOfStorms commented on GitHub (Jul 13, 2025):

This is the closest issue I could find and I assume it may be related but I haven't confirmed/gathered a lot of evidence yet to know if the things OP posted cause memory leaks. But if you leave opencode open for a long time (1d20h10m16s) I notice it running away with processes and memory/CPU consumption.

Opening htop showed tens to a hundred or so child process of cache..tui something or other running. Next time it happens I will come back and report more details on that since I did not copy or screenshot it.

When I killed opencode I noticed that it was using up ~16GB of memory at that point.

Image Image
@RingOfStorms commented on GitHub (Jul 13, 2025): This is the closest issue I could find and I assume it may be related but I haven't confirmed/gathered a lot of evidence yet to know if the things OP posted cause memory leaks. But if you leave opencode open for a long time (1d20h10m16s) I notice it running away with processes and memory/CPU consumption. Opening htop showed tens to a hundred or so child process of `cache..tui` something or other running. Next time it happens I will come back and report more details on that since I did not copy or screenshot it. When I killed opencode I noticed that it was using up ~16GB of memory at that point. <img width="286" height="313" alt="Image" src="https://github.com/user-attachments/assets/d9118de8-982f-4ab5-8e40-276dce9a6eb7" /> <img width="283" height="341" alt="Image" src="https://github.com/user-attachments/assets/23930067-d5da-48f4-b441-f7f7b9ace568" />
yindo commented 2026-02-16 17:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@RingOfStorms commented on GitHub (Jul 14, 2025):

After 9h40m59s hours of leaving open code open
Image

USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
josh     1847241 99.4  1.7 78635084 1131508 pts/3 Sl+ Jul13 577:03 opencode
josh     1847313  152  0.0 1580444 58220 pts/3   Sl+  Jul13 887:40 /home/josh/.cache/opencode/tui/tui-63z1eeqs.

I will add I think it is related to spawning LSP servers which seems related to the OP. Even after exiting open code the clippy-drivers/rust-analyzer for my rust projects stays open in processes using a bunch of CPU and memory as well.

@RingOfStorms commented on GitHub (Jul 14, 2025): After 9h40m59s hours of leaving open code open <img width="1157" height="662" alt="Image" src="https://github.com/user-attachments/assets/30370e7d-3cd9-4e57-98ab-5ae024e91f11" /> ``` USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND josh 1847241 99.4 1.7 78635084 1131508 pts/3 Sl+ Jul13 577:03 opencode josh 1847313 152 0.0 1580444 58220 pts/3 Sl+ Jul13 887:40 /home/josh/.cache/opencode/tui/tui-63z1eeqs. ``` I will add I think it is related to spawning LSP servers which seems related to the OP. Even after exiting open code the clippy-drivers/rust-analyzer for my rust projects stays open in processes using a bunch of CPU and memory as well.
yindo commented 2026-02-16 17:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@almirsarajcic commented on GitHub (Jul 17, 2025):

For me, in a few sessions, it started hanging, just writing working... without giving me any response for prolonged periods. I don't think my case was related to usage limits because in another session I was running in parallel, it was working at that time.

When I ran opencode auth and logged in with my Claude Code subscription, the problem seemed to have disappeared. I'll post if it continues.

Nope, logging in again didn't help. I've encountered the issue again, but haven't had logging enabled. I'll update with logs when I come across it again.

Image

Seems like in my case, it hangs when I'm idle for a few minutes and ask it something again.

@almirsarajcic commented on GitHub (Jul 17, 2025): ~~For me, in a few sessions, it started hanging, just writing `working...` without giving me any response for prolonged periods. I don't think my case was related to usage limits because in another session I was running in parallel, it was working at that time.~~ ~~When I ran `opencode auth` and logged in with my Claude Code subscription, the problem seemed to have disappeared. I'll post if it continues.~~ Nope, logging in again didn't help. I've encountered the issue again, but haven't had logging enabled. I'll update with logs when I come across it again. <img width="815" height="79" alt="Image" src="https://github.com/user-attachments/assets/f94bc40b-7efa-48a3-ae26-9a8ff0409d89" /> Seems like in my case, it hangs when I'm idle for a few minutes and ask it something again.
yindo commented 2026-02-16 17:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@RingOfStorms commented on GitHub (Jul 21, 2025):

I believe my stuff has been fixed in the latest versions, seems like stability with LSPs was my main issue that got many improvements the last week.

@RingOfStorms commented on GitHub (Jul 21, 2025): I believe my stuff has been fixed in the latest versions, seems like stability with LSPs was my main issue that got many improvements the last week.
yindo commented 2026-02-16 17:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#531
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?