[GH-ISSUE #344] Git commit causes memory overflow #121

New issue

Open

opened 2026-03-02 04:11:58 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 04:11:58 +03:00

Owner

Originally created by @wangkaizhuang on GitHub (Jan 13, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/344

After committing to Git, I found my computer freezing. Upon checking the memory usage, I suspected that it was caused by an infinite loop in Git-AI

Originally created by @wangkaizhuang on GitHub (Jan 13, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/344 <img width="1057" height="640" alt="Image" src="https://github.com/user-attachments/assets/d4695f87-cdc1-4d21-ae7e-f1e78e5c2f2d" /> After committing to Git, I found my computer freezing. Upon checking the memory usage, I suspected that it was caused by an infinite loop in Git-AI

kerem commented

2026-03-02 04:11:59 +03:00

Author

Owner

@wangkaizhuang commented on GitHub (Jan 13, 2026):

The memory usage issue is extremely unreasonable, and I am skeptical about it

@wangkaizhuang commented on GitHub (Jan 13, 2026): <img width="1057" height="640" alt="Image" src="https://github.com/user-attachments/assets/df5dc47c-7399-4225-bef2-29a919604364" /> The memory usage issue is extremely unreasonable, and I am skeptical about it

kerem commented

2026-03-02 04:12:00 +03:00

Author

Owner

@svarlamov commented on GitHub (Jan 13, 2026):

Hi @wangkaizhuang, I'm sorry to hear you're running into this issue. It's indeed quite out of the ordinary to see such memory usage and you're absolutely right to be frustrated. To help us investigate, could you share some more background on the commit? Was it an ordinary commit? How many files were changed? Did you have very long threads with the agents? We are shipping some major optimizations to this logic this week as we have heard that some users have ended up with extremely large checkpoints from long/loop-based agent threads. The issue, as I've seen it so far, is not the actual git ai processing logic, but simply the amount of data that the CLI is trying to load in at once.

If you're open to it, please send over your .git/ai folder from this repo to sasha at usegitai.com (only if these files and conversations you had are not confidential)

@svarlamov commented on GitHub (Jan 13, 2026): Hi @wangkaizhuang, I'm sorry to hear you're running into this issue. It's indeed quite out of the ordinary to see such memory usage and you're absolutely right to be frustrated. To help us investigate, could you share some more background on the commit? Was it an ordinary commit? How many files were changed? Did you have very long threads with the agents? We are shipping some major optimizations to this logic this week as we have heard that some users have ended up with extremely large checkpoints from long/loop-based agent threads. The issue, as I've seen it so far, is not the actual git ai processing logic, but simply the amount of data that the CLI is trying to load in at once. If you're open to it, please send over your .git/ai folder from this repo to sasha at usegitai.com (only if these files and conversations you had are not confidential)

kerem commented

2026-03-02 04:12:00 +03:00

Author

Owner

@wangkaizhuang commented on GitHub (Jan 14, 2026):

I submit more files, but I understand that this is a regular iterative task. I didn't feel any sluggishness when using Git before, and the memory usage of over 50G is outrageous to me. I have sent you my AI files

@wangkaizhuang commented on GitHub (Jan 14, 2026): I submit more files, but I understand that this is a regular iterative task. I didn't feel any sluggishness when using Git before, and the memory usage of over 50G is outrageous to me. I have sent you my AI files