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

Re: Huge possible memory leak while cherry-picking.

From
Лежанкин Иван <abyss.7@gmail.com>
Date
Aug 12, 2013, 10:04 UTC
Message-ID
<CAJc7Lbrmsna4u4s+fdCGZ7jn9HzgZkinL3tbjbjcuw40Of5umg@mail.gmail.com>
In-Reply-To
<CAMP44s282DD+tQUgVHawdRDJayjTxMjOu_R3robbCVhkbksEtQ@mail.gmail.com>

Thank you, it works very well! Will this patch go to upstream?

Also, there is still some unexpected memory consumption - about 2Gb per ~200 commits, but it's bearable. I will do a futher investigation.

Felipe, should I exclude you from my futher reports on possible memory leaks?
On 10 August 2013 00:39, Felipe Contreras <felipe.contreras@gmail.com> wrote:
Show 10 quoted lines
> On Fri, Aug 9, 2013 at 7:13 AM, Лежанкин Иван <abyss.7@gmail.com> wrote:
>> I have tried to cherry-pick a range of ~200 commits from one branch to
>> another. And you can't imagine how I was surprised when the git
>> process ate 8 Gb of RAM and died - before cherry-picking was complete.
>
> Try this:
> http://article.gmane.org/gmane.comp.version-control.git/226757
>
> --
> Felipe Contreras
Previous: Felipe ContrerasNext: Felipe Contreras
Message 3 of 9 in “Huge possible memory leak while cherry-picking.”
  1. Лежанкин ИванAug 9, 2013
  2. Felipe ContrerasAug 9, 2013
  3. Лежанкин ИванAug 12, 2013
  4. Felipe ContrerasAug 12, 2013
  5. unpack-trees: plug a memory leakRené Scharfe, Aug 13, 2013
  6. Junio C HamanoAug 13, 2013
  7. René ScharfeAug 13, 2013
  8. Junio C HamanoAug 13, 2013
  9. Felipe ContrerasAug 12, 2013

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.