Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix crash [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25245•Fetched 2026-04-13 05:45:31
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
ezekielchowworkezekielchowwork
Participants
ezekielchowworkezekielchowwork
Timeline (top)
labeled ×2

Error Message

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

RAW_BUFFERClick to expand / collapse

What happened?

Type your message or @path/to/file <--- Last few GCs --->▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ workspace (/directory) branch sandbox /model quota [31216:00000214E2219000] 147433642 ms: Mark-Compact 10198.1 (10229.0) -> 10108.7 (10158.2) MB, pooled: 1 MB, 132.20 / 0.08 ms (average mu = 0.996, current mu = 0.997) allocation failure; scavenge might not succeed [31216:00000214E2219000] 147434061 ms: Mark-Compact 10180.8 (10227.8) -> 10178.0 (10224.0) MB, pooled: 5 MB, 305.12 / 0.00 ms (average mu = 0.983, current mu = 0.272) external memory pressure; scavenge might not succeed

<--- JS stacktrace --->

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

1: 00007FF709FD18E7 node::SetCppgcReference+18263 2: 00007FF709F3212B v8::base::CPU::num_virtual_address_bits+103083 3: 00007FF70AB3AE51 v8::Isolate::ReportExternalAllocationLimitReached+65 4: 00007FF70AB27916 v8::Function::Experimental_IsNopFunction+3302 5: 00007FF70A984060 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+33904 6: 00007FF70A9806EA v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+19194 7: 00007FF70A97E583 v8::internal::StrongRootAllocatorBase::StrongRootAllocatorBase+10643 8: 00007FF70A88231B v8::Context::GetIsolate+193147 9: 00007FF70AB37402 v8::ArrayBuffer::NewBackingStore+82 10: 00007FF709DBAD87 RSA_meth_get_flags+25991 11: 00007FF709DB6DE7 RSA_meth_get_flags+9703 12: 00007FF6AAB0FA64

What did you expect to happen?

restart

Client information

  • CLI Version: 0.42.0
  • Git Commit: 68e2196d5
  • Session ID: ffee2f63-b94f-4d04-be31-22f2c3a087a9
  • Operating System: win32 v22.22.0
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 691.8 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The issue may be resolved by updating the CLI version or providing more information, such as the exported chat history JSON file, to help diagnose the problem.

Guidance

  • The crash could be related to the specific CLI version (0.37.1) or the model version (gemini-3-flash-preview), so checking for updates or trying a different version might help.
  • Providing the exported chat history JSON file as requested could give more insight into the issue and help diagnose the problem.
  • Checking the memory usage (currently 769.6 MB) and system resources might help identify if the crash is related to resource constraints.
  • Trying the solution in a different environment or setup (e.g., different operating system or IDE client) could help isolate the issue.

Notes

The issue lacks specific details about the crash, such as error messages or stack traces, which makes it difficult to provide a more targeted solution.

Recommendation

Apply workaround: Provide the exported chat history JSON file to help diagnose the issue, as this may give more insight into the problem and help resolve the crash.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING