Memory leak

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Jan 20, 2026, 09:49 UTC
Message-ID: <20260120094957.28855-1-haraldnordgren@gmail.com>
In-Reply-To: <20260119051406.GA1115353@coredump.intra.peff.net>

Show 6 quoted lines

> This is due to some memory-management hackery in e291c75a95 (remote.c:
> add branch_get_push, 2015-05-21). The good news is that not only is it
> not too hard to untangle this, but it is closely related to leaks you
> are seeing on your topic.
> 
> I'll post a series in a moment fixing both.

This seems to not have helped my memory leak. I squashed and applied your commits on top of my work as a separate pull request on GitHub, the CI leak tests are still failing:

https://github.com/git/git/pull/2170

Harald

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