gemini-cli - 💡(How to fix) Fix [Memory Spike 7.46GB] Model mismatch (Config 1.5 vs CLI 3.1-lite)

Official PRs (…)
ON THIS PAGE

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…
RAW_BUFFERClick to expand / collapse

What happened?

「実行中に7.46GBのメモリ使用警告が出たが、/bug実行時は226MBだった。また、configで1.5-flashを指定しているが3.1-lite-previewが動作している」

[ACTION REQUIRED] 📎 PLEASE ATTACH THE EXPORTED CHAT HISTORY JSON FILE TO THIS ISSUE IF YOU FEEL COMFORTABLE SHARING IT.

What did you expect to happen?

Resource Stability: Memory usage should remain stable (ideally below 1 GB) during continuous operation of the trading bot and news analysis.

Client information

  • CLI Version: 0.41.2
  • Git Commit: b0c7a1722
  • Session ID: 25ca165f-f2d9-4572-b2db-a0b59db15e6f
  • Operating System: win32 v24.15.0
  • Sandbox Environment: no sandbox
  • Model Version: gemini-3.1-flash-lite-preview
  • Auth Type: gemini-api-key
  • Memory Usage: 226.1 MB
  • Terminal Name: Unknown
  • Terminal Background: Unknown
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

No response

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

gemini-cli - 💡(How to fix) Fix [Memory Spike 7.46GB] Model mismatch (Config 1.5 vs CLI 3.1-lite)