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

Opencode processes survive terminal disconnect, become orphans, and leak memory #8948

New Issue
Open
opened 2026-02-16 18:11:14 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @ErcinDedeoglu on GitHub (Feb 9, 2026).

Originally assigned to: @rekram1-node on GitHub.

Summary

When a terminal session is closed or an SSH connection drops without explicitly exiting opencode (Ctrl+C / exit), the opencode process is not terminated. It becomes an orphan (reparented to PID 1), continues to hold memory indefinitely, and leaks memory over time. On long-running dev machines, this leads to severe memory exhaustion.

Environment

  • opencode version: 1.1.53
  • Binary: Bun 1.2 compiled, ELF aarch64
  • OS: Ubuntu 22.04.5 LTS (ARM64, Orange Pi)
  • RAM: 32 GB

Reproduction

  1. Open a terminal (SSH or local)
  2. Run opencode
  3. Use it for a while (interact with an agent, run tools, etc.)
  4. Close the terminal window or disconnect SSH without exiting opencode
  5. Observe: the opencode process continues running, detached from any TTY

Repeat a few times and watch memory disappear.

Observed Behavior

After a day and a half of normal usage (opening/closing sessions), 6 orphaned opencode processes accumulated:

PID Age RSS TTY PPID State
140728 1d 17h 504 MB ? (none) 1 (init) Sleeping
700891 1d 12h 11.2 GB ? (none) 1 (init) Sleeping
254506 1d 16h 499 MB ? (none) 1 (init) Sleeping
715951 1d 12h 2.5 GB ? (none) 1 (init) Sleeping
1388538 21h 4.1 GB ? (none) 1 (init) Sleeping
1703444 3 min 467 MB ? (none) 1 (init) Sleeping

Total orphaned memory: ~19 GB out of 32 GB, making the machine nearly unusable.

Only 2 processes were actually attached to terminals and doing work.

Signal Analysis

SigIgn: 0000000001000000  (only signal 25 ignored)
SigCgt: 0000000128005cef  (SIGHUP is CAUGHT, not ignored)

SIGHUP (signal 1) is registered as caught, which means the process receives it on terminal disconnect — but it does not exit. The handler appears to swallow the signal without performing a clean shutdown.

Memory Leak

The oldest process (36h) grew to 11.2 GB RSS with 210 open file descriptors, while younger processes of similar age sat at ~500 MB. This suggests a memory leak in long-running sessions, likely from accumulated conversation context, MCP tool results, or unreleased buffers.

Expected Behavior

  1. On SIGHUP (terminal disconnect): opencode should clean up and exit within a reasonable timeout (e.g., 5-10 seconds)
  2. If graceful shutdown hangs (waiting on MCP servers, API calls, etc.): force exit after timeout
  3. Long-running sessions should not grow unboundedly in memory — there should be some form of context/buffer pruning or ceiling

Workaround

Manually kill orphaned processes:

# Find orphaned opencode processes (PPID=1, no TTY)
ps -eo pid,ppid,tty,rss,comm | grep opencode | awk '$2 == 1 && $3 == "?" {print $1}' | xargs kill

Impact

On resource-constrained machines (ARM SBCs, small VMs) this is particularly painful — a few forgotten sessions can OOM the machine within a day.

Originally created by @ErcinDedeoglu on GitHub (Feb 9, 2026). Originally assigned to: @rekram1-node on GitHub. ## Summary When a terminal session is closed or an SSH connection drops without explicitly exiting opencode (`Ctrl+C` / `exit`), the opencode process is not terminated. It becomes an orphan (reparented to PID 1), continues to hold memory indefinitely, and leaks memory over time. On long-running dev machines, this leads to severe memory exhaustion. ## Environment - **opencode version**: 1.1.53 - **Binary**: Bun 1.2 compiled, ELF aarch64 - **OS**: Ubuntu 22.04.5 LTS (ARM64, Orange Pi) - **RAM**: 32 GB ## Reproduction 1. Open a terminal (SSH or local) 2. Run `opencode` 3. Use it for a while (interact with an agent, run tools, etc.) 4. **Close the terminal window** or **disconnect SSH** without exiting opencode 5. Observe: the opencode process continues running, detached from any TTY Repeat a few times and watch memory disappear. ## Observed Behavior After a day and a half of normal usage (opening/closing sessions), 6 orphaned opencode processes accumulated: | PID | Age | RSS | TTY | PPID | State | |-----|-----|-----|-----|------|-------| | 140728 | 1d 17h | 504 MB | ? (none) | 1 (init) | Sleeping | | 700891 | 1d 12h | **11.2 GB** | ? (none) | 1 (init) | Sleeping | | 254506 | 1d 16h | 499 MB | ? (none) | 1 (init) | Sleeping | | 715951 | 1d 12h | 2.5 GB | ? (none) | 1 (init) | Sleeping | | 1388538 | 21h | 4.1 GB | ? (none) | 1 (init) | Sleeping | | 1703444 | 3 min | 467 MB | ? (none) | 1 (init) | Sleeping | **Total orphaned memory: ~19 GB out of 32 GB**, making the machine nearly unusable. Only 2 processes were actually attached to terminals and doing work. ## Signal Analysis ``` SigIgn: 0000000001000000 (only signal 25 ignored) SigCgt: 0000000128005cef (SIGHUP is CAUGHT, not ignored) ``` `SIGHUP` (signal 1) **is registered as caught**, which means the process receives it on terminal disconnect — but it does not exit. The handler appears to swallow the signal without performing a clean shutdown. ## Memory Leak The oldest process (36h) grew to **11.2 GB RSS** with **210 open file descriptors**, while younger processes of similar age sat at ~500 MB. This suggests a memory leak in long-running sessions, likely from accumulated conversation context, MCP tool results, or unreleased buffers. ## Expected Behavior 1. On `SIGHUP` (terminal disconnect): opencode should **clean up and exit** within a reasonable timeout (e.g., 5-10 seconds) 2. If graceful shutdown hangs (waiting on MCP servers, API calls, etc.): **force exit** after timeout 3. Long-running sessions should not grow unboundedly in memory — there should be some form of context/buffer pruning or ceiling ## Workaround Manually kill orphaned processes: ```bash # Find orphaned opencode processes (PPID=1, no TTY) ps -eo pid,ppid,tty,rss,comm | grep opencode | awk '$2 == 1 && $3 == "?" {print $1}' | xargs kill ``` ## Impact On resource-constrained machines (ARM SBCs, small VMs) this is particularly painful — a few forgotten sessions can OOM the machine within a day.
yindo added the perf label 2026-02-16 18:11:14 -05:00
yindo commented 2026-02-16 18:11:14 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue appears to be a duplicate of existing reports about orphaned processes when terminals close. Please check these related issues:

  • #12767: [BUG] Opencode process survives terminal close — missing SIGHUP handler causes orphaned process accumulation
  • #10563: Memory Leak: Orphaned processes when terminal closes without explicit exit
  • #11225: [BUG]: opencode attach processes not terminated when tmux pane is killed (zombie process accumulation)

All three issues describe the same root cause: missing SIGHUP signal handling leading to orphaned processes. #12767 already has an assignee. Please consolidate efforts on one of these existing issues to avoid duplicate work.

@github-actions[bot] commented on GitHub (Feb 9, 2026): --- This issue appears to be a duplicate of existing reports about orphaned processes when terminals close. Please check these related issues: - #12767: [BUG] Opencode process survives terminal close — missing SIGHUP handler causes orphaned process accumulation - #10563: Memory Leak: Orphaned processes when terminal closes without explicit exit - #11225: [BUG]: opencode attach processes not terminated when tmux pane is killed (zombie process accumulation) All three issues describe the same root cause: missing SIGHUP signal handling leading to orphaned processes. #12767 already has an assignee. Please consolidate efforts on one of these existing issues to avoid duplicate work.
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 perf
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#8948
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?