Frequent JavaScript heap out of memory

Describe the bug

Every few minutes the copilot CLI crashes with the following output:

[2525992:0x4f1e6000]  2035407 ms: Mark-Compact 3919.7 (4098.2) -> 3918.2 (4097.4) MB, pooled: 3 MB, 227.10 / 0.00 ms  (average mu = 0.100, current mu = 0.008) allocation failure; scavenge might not succeed
[2525992:0x4f1e6000]  2035520 ms: Mark-Compact 3925.0 (4097.4) -> 3918.2 (4097.4) MB, pooled: 3 MB, 100.87 / 0.00 ms  (average mu = 0.102, current mu = 0.105) allocation failure; scavenge might not succeed

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Writing Node.js report to file: report.20260904.172737.2525992.0.001.json
Node.js report completed
----- Native stack trace -----

 1: 0x757658 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [copilot]
 2: 0xc60e30  [copilot]
 3: 0xc60f1f  [copilot]
 4: 0xf047f5  [copilot]
 5: 0xf04822  [copilot]
 6: 0xf04b1a  [copilot]
 7: 0xf1581a  [copilot]
 8: 0xf19bc0  [copilot]
 9: 0x19b78a1  [copilot]
[1]    2525992 IOT instruction (core dumped)  copilot

Affected version

GitHub Copilot CLI 1.0.83-5

Steps to reproduce the behavior

1. Initiate some work
2. Wait a few minutes

Expected behavior

don't crash.

Additional context

The CLI is executed on x86_64 Ubuntu/Linux 24.04, fully updated
It is access like Windows Terminal-->ssh-->Linux-->tmux/zsh-->CopilotCLI (no difference when running directly on the linux machine)

Have tried to use NODE_OPTIONS but it is silently ignored.

Tái hiện lỗi crash bằng cách bắt đầu công việc trong Copilot CLI 1.0.83-5 trên Ubuntu/Linux 24.04 và chờ vài phút. Bắt đầu với tệp báo cáo Node.js được tạo ra và cách CLI xử lý NODE_OPTIONS; hoàn tất khi cùng một khối lượng công việc không còn kết thúc bằng lỗi crash JavaScript heap out-of-memory.