OOM crash (`JavaScript heap out of memory`) on long `--resume` sessions; crash dumps written into the user's cwd
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- javascript, nodejs
- 領域
- cli, performance
研究方向
首先，使用 --report-on-fatalerror 和 --optimize-for-size 重現一個較長的 --resume 工作階段，然後檢查隨附的 Node 診斷報告和工作階段歷程行為。完成的標準是：長工作階段不再持續增長直到發生無法復原的 OOM，且致命錯誤報告會寫入工具擁有的位置，而不是使用者的 cwd。
由索引模型根據 Issue 內容生成。
描述
Describe the bug
Summary
Copilot CLI 1.0.82 repeatedly dies with a V8 heap OOM during long resumed sessions. It crashed 3 times in ~14 hours for me, always at the 4 GiB heap cap.
Separately, the resulting Node diagnostic reports are written into the current working directory, so they land inside whatever git repo I'm working in and show up as untracked files.
Environment
| Copilot CLI | 1.0.82 |
| Node | v24.18.1 |
| Platform | linux x64 (glibc 2.39) |
| Invocation | copilot --no-warnings --report-on-fatalerror --optimize-for-size --expose-gc copilot --resume |
What happens
"event": "Allocation failed - JavaScript heap out of memory"
"trigger": "OOMError"
Three crashes on 2 Sep 2026, all in resumed sessions:
| Time (UTC) | Heap used / limit | RSS | CPU (user s) |
|---|---|---|---|
| 00:51:37 | 3.98 / 4.00 GiB | 4.63 GiB | 7833 |
| 03:08:30 | 3.99 / 4.00 GiB | 4.75 GiB | 4065 |
| 14:39:00 | 3.99 / 4.00 GiB | 4.69 GiB | 2785 |
Diagnostic detail
At crash, old_space alone accounted for 3.96 GiB of the 3.99 GiB used:
old_space: 3.96 GiB
code_space: 0.01 GiB
trusted_space: 0.01 GiB
large_object_space: 0.00 GiB
Nearly all of it is long-lived, survived-GC data — consistent with unbounded retention/a leak rather than a transient allocation spike. javascriptStack is "No stack." / Unavailable., as expected for an OOM abort.
All three crashes were --resume sessions with substantial CPU time behind them (46m–2h11m user CPU), which points at per-session state (conversation/tool history?) accumulating without bound. Heap is pinned right at the cap each time, and RSS exceeds it by ~0.6–0.75 GiB.
Impact
- Data/work loss — long sessions die abruptly once they get big enough. The practical ceiling appears to be session length, not task complexity.
- Repo pollution — because
--report-on-fatalerroris set and Node writes reports relative to cwd, files likereport.20260902.143900.310882.0.001.jsonappear inside the user's repository. They show as untracked ingit statusand are easy to commit by accident. A CLI shouldn't drop crash artifacts into arbitrary project directories.
Notes for Copilot debugging
The 4 GiB ceiling is not user-imposed:
NODE_OPTIONSis unset.- Host has 30 GiB RAM with ~9 GiB free at crash time — no system memory pressure.
- Plain
nodeon this host reports a 4.05 GiB default heap limit;node --optimize-for-sizereports exactly 4.00 GiB, matchingjavascriptHeap.memoryLimitin every dump.
So the cap comes from the --optimize-for-size flag the CLI passes itself. The process aborts at a self-imposed ceiling while the machine still has memory to spare — worth considering whether that flag is right for long-lived sessions, though the underlying retention growth looks like the real bug.
Affected version
1.0.82
Steps to reproduce the behavior
- Start a Copilot CLI session in a git repo.
- Use it heavily / resume it over an extended period (mine ran for hours of CPU time).
- Session eventually aborts with the OOM above; a
report.*.jsonappears in the repo root.
Expected behavior
- Session memory should be bounded (evict/compact old history), or degrade gracefully instead of a hard abort.
- Crash dumps should go somewhere tool-owned — e.g.
~/.copilot/logs/or$TMPDIR— not the user's cwd. If cwd is intentional, it should be configurable.
Additional context
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 17 小時 6 分鐘
- 30 天內合併 PR
- 5
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
github/copilot-cli 的其他 Issue
-
area:sessions
難度 2/5 1-3 小時 新手友好度 72/100
github/copilot-cli#4996 ·
維護者通常 1 天內回覆
-
triage
難度 1/5 1 小時以內 新手友好度 88/100
github/copilot-cli#4963 · 1 則留言 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 75/100
github/copilot-cli#4932 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 78/100
github/copilot-cli#4909 ·
維護者通常 1 天內回覆
-
triage
難度 2/5 1-3 小時 新手友好度 76/100
github/copilot-cli#4906 ·
維護者通常 1 天內回覆
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 76/100
adobe-fonts/source-serif#152 ·
-
area:ansible source:reader type:content-error
難度 1/5 1 小時以內 新手友好度 86/100
stephrobert/blog-roadmap#42 ·
-
難度 1/5 1 小時以內 新手友好度 90/100
-
難度 2/5 1-3 小時 新手友好度 75/100
-
難度 2/5 1-3 小時 新手友好度 70/100
nolabs-ai/nono-packs#44 ·
維護者通常 1 天內回覆