Ran out of js heap

[jordanlhenderson]

What happened?

bug-report-history-1772193508386.json

traceback:

<--- Last few GCs --->

[313:0x6005e39f0e20] 15181501 ms: Scavenge (reduce) 3909.6 (4064.7) -> 3909.5 (4065.4) MB, 4.21 / 0.00 ms (average mu = 0.929, current mu = 0.959) allocation failure;
[313:0x6005e39f0e20] 15182014 ms: Mark-Compact (reduce) 4068.7 (4223.6) -> 3986.2 (4144.6) MB, 422.19 / 0.04 ms (+ 14.7 ms in 576 steps since start of marking, biggest step 0.6 ms, walltime since start of marking 848 ms) (average mu = 0.848, current mu =

<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

1: 0x792844c3a908 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/lib/x86_64-linux-gnu/libnode.so.115]
2: 0x7928451ebc30 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/lib/x86_64-linux-gnu/libnode.so.115]
3: 0x7928451ebff5 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/lib/x86_64-linux-gnu/libnode.so.115]
4: 0x7928453fa7c7 [/lib/x86_64-linux-gnu/libnode.so.115]
5: 0x7928454122a9 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.so.115]
6: 0x7928453ebcdc v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.115]
7: 0x7928453ed2e5 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/lib/x86_64-linux-gnu/libnode.so.115]
8: 0x7928453cd907 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/lib/x86_64-linux-gnu/libnode.so.115]
9: 0x79284581d73c v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/lib/x86_64-linux-gnu/libnode.so.115]
10: 0x7927e5099ef6

What did you expect to happen?

I expected it to not run our of heap

Client information

• CLI Version: 0.30.0
• Git Commit: 1e3b992
• Session ID: 371ca12d-49ed-48cf-9693-da911a323cee
• Operating System: linux v20.19.2
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-3
• Auth Type: oauth-personal
• Memory Usage: 1.31 GB
• Terminal Name: Unknown
• Terminal Background: #0c0c0c
• Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

[jacob314]

Thank you for including a history file. This makes it much more likely we will be able to reproduce the issue.

[aishop-lab]

The MemoryMonitor already has checkMemoryThreshold() which compares heap usage against a configurable threshold, and getMemoryUsageSummary() returning heap/RSS in MB. It snapshots every 10 seconds with high-water mark tracking. So the infrastructure to catch this before the OOM exists — it just isn't surfaced anywhere the user can see.

A warning level at 60% and 85% of heap limit would give users time to react before the crash.