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

Re: Regression in memory consumption of git fsck

From
Jeff King <peff@peff.net>
Date
Feb 14, 2018, 13:55 UTC
Message-ID
<20180214135551.GA27513@sigill.intra.peff.net>
In-Reply-To
<20180214124828.27845-1-szeder.dev@gmail.com>
On Wed, Feb 14, 2018 at 01:48:28PM +0100, SZEDER Gábor wrote:
Show 11 quoted lines
> > If I revert that commit (on top of current master) the memory
> > consumption goes down to 2GB again. The change looks relatively harmless
> > to me, so does anyone know what's going on here?
> 
> I could reproduce the increased memory usage even for much smaller
> repositories.  The patch below seems to fix it for me.
> 
> 
>  -- >8 --
> 
> Subject: [PATCH] fsck: plug tree buffer leak

I think this is fixed already in ba3a08ca0e (fsck: fix leak when traversing trees, 2018-01-20), which is in 'next' (and marked for "will merge to master in yesterday's "what's cooking").

-Peff
Previous: SZEDER Gábor
Message 3 of 3 in “Regression in memory consumption of git fsck”
  1. Dominic SacréFeb 14, 2018
  2. SZEDER GáborFeb 14, 2018
  3. Jeff KingFeb 14, 2018

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.