gemini-cli - 💡(How to fix) Fix FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory [1 comments, 2 participants]

What happened?

running standard commands/prompts took longer than usual to process esc'd and started again still took long then fatal error <--- Last few GCs --->

[112805:0x1b227b30] 63473098 ms: Mark-Compact 1655.2 (1835.4) -> 1639.8 (1835.4) MB, 214.94 / 0.01 ms (average mu = 0.531, current mu = 0.537) task; scavenge might not succeed [112805:0x1b227b30] 63473547 ms: Mark-Compact 1659.2 (1838.8) -> 1646.8 (1842.6) MB, 205.01 / 0.00 ms (average mu = 0.537, current mu = 0.543) allocation failure; scavenge might not succeed

<--- JS stacktrace --->

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

1: 0xb78db3 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node] 2: 0xee8300 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] 3: 0xee85e7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] 4: 0x10fb205 [/usr/bin/node] 5: 0x1113088 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node] 6: 0x10e91f1 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node] 7: 0x10ea385 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node] 8: 0x10c69a6 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node] 9: 0x10b8304 v8::internal::FactoryBasev8::internal::Factory::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [/usr/bin/node] 10: 0x10bb667 v8::internal::FactoryBasev8::internal::Factory::NewRawTwoByteString(int, v8::internal::AllocationType) [/usr/bin/node] 11: 0x140ce75 v8::internal::String::SlowFlatten(v8::internal::Isolate*, v8::internal::Handlev8::internal::ConsString, v8::internal::AllocationType) [/usr/bin/node] 12: 0x10cb48c v8::internal::Factory::NewProperSubString(v8::internal::Handlev8::internal::String, int, int) [/usr/bin/node] 13: 0x1545dba v8::internal::Runtime_StringSubstring(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node] 14: 0x195e476 [/usr/bin/node]

What did you expect to happen?

process the prompt

Client information

• CLI Version: 0.42.0
• Git Commit: 68e2196d5
• Session ID: bb278696-fc07-4276-95c1-0fdce48396a9
• Operating System: linux v20.20.2
• Sandbox Environment: no sandbox
• Model Version: auto-gemini-3
• Auth Type: oauth-personal
• Memory Usage: 466.8 MB
• Terminal Name: Unknown
• Terminal Background: #000000
• Kitty Keyboard Protocol: Unsupported

Login information

google auth

Anything else we need to know?

i am trying to attached .heapsnapshot but get this error: Error File type .heapsnapshot not supported. See the documentation for supported file types.