[Bug] OpenCode adapter leaks ChildProcess exit listeners until an LXC host freezes: "11 exit listeners added to [ChildProcess]"
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 45/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- node.js, typescript
調査の方向性
Start by locating the OpenCode adapter’s ChildProcess exit listener registration and tracing how recoverShells, event-stream reconnects, and borrowed-session opens reuse child handles. Check whether listeners remain attached after exit or are added again to the same child; the issue does not name source files or tests. Done when repeated reconnect and retry paths do not accumulate exit listeners or retain exited child processes.
索引モデルが issue の本文から書いたものです。
説明
[Bug] t3code.service leaks ChildProcess exit listeners until the whole LXC freezes: MaxListenersExceededWarning ... 11 exit listeners added to [ChildProcess]
Environment
- T3 Code Server
t3 serve --host 0.0.0.0 --base-dir /opt/t3code, systemd system unitt3code.service, Debian 13 inside an unprivileged Proxmox LXC (6 vCPU, 16 GiB), node v24.22.3 bundled SEA binary. - Reproduced on
0.1.10(npm view t3 dist-tags.latest= 0.1.10, so no stable upgrade exists). A test runtime0.1.11-nightly.20261119.4928was installed on 2026-11-19 08:32 EST to see whether it still leaks; results below. - Provider: OpenCode adapter (
opencode servechildren +opencode-pty).
What happened
The container froze completely twice on 2026-11-19 (06:44 and ~07:20 EST) and twice on 2026-11-17 (00:56, 04:16). Nothing self-healed: the guest journal goes silent roughly 20 minutes before a human has to force a stop/start from the Proxmox side (vzstop:4038:root@pam 07:07:45 + vzstart 07:07:52, again 08:07:58 + 08:08:12). Inside the guest the journal simply ends (06:49:04, 07:42:04) with no shutdown lines, and lxc-stop returns in ~3 s because all that RAM vanishes at once.
Numbers (container-scoped node_exporter, 5-min samples):
06:40 MemAvailable 7168 MiB AnonPages 2337 MiB Active_anon 967 MiB load1 4.5
06:45 MemAvailable 2925 MiB AnonPages 6552 MiB Active_anon 5581 MiB load1 13.5 procs_running 21
06:50 MemAvailable 780 MiB load1 77.7 procs_blocked 11
07:10 MemAvailable 4743 MiB (after a forced restart)
07:30 MemAvailable 563 MiB (growth resumed immediately)
While frozen, node_pressure_io_stalled_seconds_total and node_pressure_memory_stalled_seconds_total repeat identical values (06:44-06:52) - even node_exporter was blocked, which is why the guest stops logging while Proxmox still sees a live PID.
The signature points at ChildProcess exit listeners
The server logs itself, minutes before each cliff:
2026-11-19T05:13:56 t3[411515]: (node:411515) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 exit listeners added to [ChildProcess]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
2026-11-19T06:44:00 t3[411515]: (node:411515) MaxListenersExceededWarning: ... same ...
2026-11-19T08:09:16 t3[404]: (node:404) MaxListenersExceededWarning: ... same ...
06:44:00 is five minutes before the 06:45 cliff. The same process also logs WARN (#9692): Lost the OpenCode event stream; reconnecting. (5 occurrences over 3 days) and a 54-line storm of
TimeoutError: Operation timed out after '5s'
at OpenCode2Adapter.recoverShells (file:///root/.t3/runtime/versions/0.1.10/t3:426721:50)
at OpenCode2Adapter.openSession (...:427739:19)
at OpenCode2Adapter.borrowAndOpenSession (...:431816:81)
at ProviderInstallationGate.execute (...:274260:45)
at orchestrationV2.providerTurnStart.start (...:363638:268)
so listeners appear to be re-added on every event-stream reconnect / recoverShells retry / borrowed-session open, on ChildProcess objects that stay referenced.
Growth is steep and starts from a cold idle start: after the 08:19:55 restart, systemctl show t3code -p MemoryCurrent -p MemoryPeak went 742 MiB -> 1.99 GiB MemoryPeak within 9 minutes, RSS being ~480 MiB in the node main process + ~330 MiB in one opencode child, with no thread doing heavy work. It is the top-RSS process in the container by 3x.
Ruled out on our side (so this is not a workload report)
- Disk: root 126 GiB with 23 GiB free (82 %).
- Host: hypervisor up 17 days, no
hung_task/ata/I/O-error kernel lines,smartctlPASSED on all three disks, no ZFS. - cgroup OOM:
/sys/fs/cgroup/lxc/4038/memory.eventsshowsoom 0 oom_kill 0- the kernel never killed anything, the box just thrashed (5.5 GiB of container swap in use). - Coredumps: none.
lxcfs:NRestarts=0. A per-unit sampler confirms the growth is insidet3code.service, not in any other service, and it is anonymous heap (not page cache, not/tmptmpfs, which stayed flat at 7355 MiB available across the cliff). - The OpenCode reconnect symptom matches closed #37396; the listener accumulation and the RAM growth do not appear to be covered there, and no existing issue mentions
exit listenersorChildProcesslisteners.
Asks
- Detach (or use
{once:true}for) theexitlisteners registered on OpenCode / providerChildProcesshandles when the child exits, and de-duplicate registration per child instead of per reconnect - the warning names the exact emitter, so it should be findable. - Consider a defensive
setMaxListenersonly as a symptom mask; the leak of the retainedChildProcess+ closure is the RAM cost, and 0.1.10 will happily reach the container limit. - Nice to have: log per-adapter retained-process counts (or expose them via a debug endpoint) so operators can attribute growth without a 3-day Prometheus history.
Workaround in place
/etc/systemd/system/t3code.service.d/memory-cap.conf = MemoryHigh=4G, MemoryMax=6G, OOMPolicy=stop, Restart=always, RestartSec=5, so the server is killed and back in ~5 s instead of freezing the whole container until someone presses Restart in the hypervisor UI. A V8 --max-old-space-size cap was rejected because the binary is a node SEA bundle and NODE_OPTIONS inheritance to its opencode children is not reliable.
- 主要言語
- TypeScript
- スター
- 24.8k
- フォーク
- 6.4k
- 平均マージ
- 4時間 29分
- マージ済み PR(30日)
- 488
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pingdotgg/t3code のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 1 日以内に返信
-
needs more info
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
pingdotgg/t3code#39400 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
[Bug]: Wrapped PR titles lose bottom padding in the thread details panel対応中かも @iamdatvt94 が 1 日前に担当しました。 オープンbug needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
bug needs-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
メンテナーはふだん 1 日以内に返信
pingdotgg/t3code の issue をすべて見る
似ている issue
-
area:plugins kind:bug priority:p2 ready
難易度 2/5 1〜3時間 初心者へのやさしさ 90/100
メンテナーはふだん 1 日以内に返信
-
Escaped `*` followed by `*` (`\**`) never matches対応中かも @bardrop が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 71/100
editorconfig/editorconfig-core-js#172 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
vega/vega-webgpu#40 ·
-
type: bug 🐛
難易度 2/5 1〜3時間 初心者へのやさしさ 63/100
puckeditor/puck#1929 ·
メンテナーはふだん 1 日以内に返信
-
compression() compresses every response at Brotli quality 11対応中かも @staylor が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信