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

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Oct 2, 2026, 19:28 UTC
Message-ID: <asAF7D_XefgKtgf6@fruit.crustytoothpaste.net>
In-Reply-To: <BL0PR05MB5603A8CE8FD78127FB810BE2D8892@BL0PR05MB5603.namprd05.prod.outlook.com>

On 2026-10-02 at 11:04:00, Pierre Bruno wrote:

Show 19 quoted lines

> 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.

I think you omitted the attachment, but in any event, I would say that this is not normally expected for `git status`. We'd really need to know what the command line of those processes is for us to know what they're for; for instance, you may be triggering maintenance on the repository, in which case packing a large repository could legitimately use that much memory. Similarly, if you're using a file system monitor process, that could consume a large amount of memory in a large repository.

I don't personally use Windows, so I'm afraid I can't tell you how to get that information there. Once you have it, though, it should be clearer if that's a reasonable amount of memory to be using given the size of your repository.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA