git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Windows: ~1 GB RAM per git process, many concurrent (2.56.0.windows.1)

From
PBPierre Bruno <pierrebruno@hotmail.ch>
Date
Oct 2, 2026, 11:04 UTC
Message-ID
<BL0PR05MB5603A8CE8FD78127FB810BE2D8892@BL0PR05MB5603.namprd05.prod.outlook.com>
Hi,

On Windows, git status-type commands use about 1 GB of RAM per process, and dozens run at once when I use coding agents (OpenCode and Oh My Pi) in a repository. CPU is near 0%, disk I/O is steady, and the total is several GB. Since two unrelated tools cause it, I suspect git or my repo.

Expected: a few short-lived git processes with far less memory.
git version 2.56.0.windows.1 (commit 49d759b698127791a5f3f2759c69b983846711dd,
fsmonitor--daemon enabled), Windows <version>
Repo: <N files / GB>, <N> untracked files
Manual 'git status' with no other tool running: <fast/slow, memory>
Stable 2.55.0: <same/different>
Command line seen in Task Manager: <paste>

Is ~1 GB per process expected here, and is there a recommended config to reduce it? Full 'git bugreport' attached.

Thanks, Pierre Bruno

Next: brian m. carlson
Message 1 of 3 in “Windows: ~1 GB RAM per git process, many concurrent (2.56.0.windows.1)”
  1. Pierre BrunoOct 2, 2026
  2. brian m. carlsonOct 2, 2026
  3. Jeff KingOct 2, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.