crash report (memory leak)

[bernoussama]

Summary

Command code crashed after clicking ctrl+o to see thinking traces and it crashed as thinking was streaming

Expected Behavior

see thinking detail

Actual Behavior

crash

Steps to reproduce the issue

1. Send prompt in command code.(after some time running in the background 15+ mins)
2. Click Ctrl+O to see agent thinking.
3. See thinking traces streaming.
4. Crash

Command Code Version

0.26.25

Operating System

Linux

Terminal/IDE

tmux

Shell

bash

Additional context

the error log after it crashes:

<--- Last few GCs --->

[100969:0x1e04d000]  9760259 ms: Mark-Compact 4053.6 (4116.4) -> 4040.5 (4117.4) MB, pooled: 0 MB, 242.35 / 0.44 ms  (average mu = 0.257, current mu = 0.194) task; scavenge might not succeed
[100969:0x1e04d000]  9760603 ms: Mark-Compact 4055.7 (4117.4) -> 4041.2 (4150.1) MB, pooled: 0 MB, 255.09 / 0.44 ms  (average mu = 0.259, current mu = 0.260) task; scavenge might not succeed

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

 1: 0x72be1c node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xb9dc10  [node]
 3: 0xb9dcff  [node]
 4: 0xe367e5  [node]
 5: 0xe36812  [node]
 6: 0xe36b0a  [node]
 7: 0xe4702a  [node]
 8: 0xe4b3d0  [node]
 9: 0x18de281  [node]
Aborted                    (core dumped) cmd

Looks like a memory leak