google-gemini / google-gemini/gemini-cli
High memory usage detected
- Dominant language
- TypeScript
- Stars
- 107k
- Forks
- 14.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 45
Description
### What happened?
[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?
Loop over process during break time incresing memory usage
### Client information
* **CLI Version:** 0.53.1
* **Git Commit:** 19a68016b
* **Session ID:** 022054a7-fb28-4d03-a337-38ea7ed0a88d
* **Operating System:** win32 v24.17.0
* **Sandbox Environment:** no sandbox
* **Model Version:** gemini-3.1-flash-lite
* **Auth Type:** gemini-api-key
* **Memory Usage:** 7.53 GB
* **Terminal Name:** Unknown
* **Terminal Background:** #f9f9f9
* **Kitty Keyboard Protocol:** Unsupported
### Login information
_No response_
### Anything else we need to know?
_No response_
Contributor guide
Research direction
No source file, entry point, or test is named. Start by reproducing the memory increase in gemini-cli 0.53.1 on win32 while the process is idle, using the exported chat-history JSON if available, then trace the relevant CLI loop. Done means the growth is reproducible, its cause is identified, and the fix is verified without continued memory increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100