Issue Station
Sign In
Tools hereToolbox

gemini-cli - 💡(How to fix) Fix 100% cpu usage at start, extremely sluggish

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

What happened?

I started gemini cli

What did you expect to happen?

Nearly 0 cpu usage

Client information

  • CLI Version: 0.40.1
  • Git Commit: N/A
  • Session ID: 9665055e-4708-4d5b-9c4a-137819039c00
  • Operating System: linux v22.22.2
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 756.4 MB
  • Terminal Name: VTE(8202)
  • Terminal Background: #000000
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

Killing it and restarting it doesn't help. Using strace shows it endlessly rereading the session chats. Deleting all the chats brought it back to normal.

There weren't a lot of chats, I've been using gemini for a couple weeks, one session at a time.

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…
#callback error#memory management#API rate limit#retriever error#indexing error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING