high memory

### What happened?

--- Last few GCs --->

[20492:000002D35B06C000] 9058623 ms: Mark-Compact 8043.1 (8112.4) -> 8039.7 (8112.4) MB, pooled: 0.5 MB, 347.94 / 0.00 ms (average mu = 0.125, current mu = 0.044) allocation failure; scavenge might not succeed
[20492:000002D35B06C000] 9058927 ms: Incremental Mark-Compact (reduce) 8044.0 (8113.2) -> 8042.6 (8106.2) MB, pooled: 0.0 MB, 187.96 / 0.00 ms (+ 36.2 ms in 59 steps since start of marking, biggest step 5.0 ms, walltime since start of marking 247 ms) (av
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 00007FF7D7E059C9 node::OnFatalError+1289
2: 00007FF7D663C10A v8::Function::NewInstance+522
3: 00007FF7D643C8E7 X509_STORE_get_cert_crl+54215
4: 00007FF7D643A4DC X509_STORE_get_cert_crl+44988
5: 00007FF7D64537F0 X509_STORE_set_cleanup+432
6: 00007FF7D6453FC9 X509_STORE_set_cleanup+2441
7: 00007FF7D6453DC1 X509_STORE_set_cleanup+1921
8: 00007FF7D64538D3 X509_STORE_set_cleanup+659
9: 00007FF7D64633B6 X509_CRL_set_meth_data+27574
10: 00007FF7D648189E X509_CRL_set_meth_data+151710
11: 00007FF7D64817FB X509_CRL_set_meth_data+151547
12: 00007FF7D6467A1D X509_CRL_set_meth_data+45597
13: 00007FF7D6467B44 X509_CRL_set_meth_data+45892
14: 00007FF7D62C43F5 v8::Promise::MarkAsSilent+220981
15: 00007FF7D62CA88C v8::Promise::MarkAsSilent+246732
16: 00007FF7D65F1DC1 v8::internal::Xsum::Round+1313
17: 000002D31FE7F37A

### What did you expect to happen?

I think I gave it too broad of a task. It warned me about high memory usage and a little while later had a fatal error. Reporting because it asked for it. Heres the last log, I guess it couldn't compact:

### Client information

* **CLI Version:** 0.55.1
* **Git Commit:** 41327e407
* **Session ID:** b756ca14-9128-40a3-9032-399af346efd7
* **Operating System:** win32 v26.2.0
* **Sandbox Environment:** no sandbox
* **Model Version:** auto
* **Auth Type:** gemini-api-key
* **Memory Usage:** 268.9 MB
* **Terminal Name:** Unknown
* **Terminal Background:** #0c0c0c
* **Kitty Keyboard Protocol:** Unsupported

### Login information

_No response_

### Anything else we need to know?

_No response_

No source file, test, or reproducible task is identified. Start by reproducing the broad-task failure with CLI version 0.55.1 on Windows and capture memory behavior and logs; then trace the operation that grows the heap. Done means identifying the trigger, preventing the out-of-memory failure, and adding a regression test.

Written by the indexing model from the issue text.