Re: Huge possible memory leak while cherry-picking.

2013-08-12 Thread Felipe Contreras
On Mon, Aug 12, 2013 at 5:04 AM, Лежанкин Иван wrote: > Thank you, it works very well! > Will this patch go to upstream? Ask Junio. > Also, there is still some unexpected memory consumption - about 2Gb > per ~200 commits, but it's bearable. > I will do a futher investigation. Can you post some

Re: Huge possible memory leak while cherry-picking.

2013-08-12 Thread Felipe Contreras
On Mon, Aug 12, 2013 at 5:04 AM, Лежанкин Иван wrote: > Thank you, it works very well! > Will this patch go to upstream? Ask Junio. > Also, there is still some unexpected memory consumption - about 2Gb > per ~200 commits, but it's bearable. > I will do a futher investigation. Can you post some

Re: Huge possible memory leak while cherry-picking.

2013-08-12 Thread Лежанкин Иван
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 201

Re: Huge possible memory leak while cherry-picking.

2013-08-09 Thread Felipe Contreras
On Fri, Aug 9, 2013 at 7:13 AM, Лежанкин Иван 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.o

Huge possible memory leak while cherry-picking.

2013-08-09 Thread Лежанкин Иван
Hi, 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. I downloaded git sources from master and built it with gperftools support (-ltcmalloc).