Re: Huge possible memory leak while cherry-picking.
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.contre...@gmail.com wrote: On Fri, Aug 9, 2013 at 7:13 AM, Лежанкин Иван abys...@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 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huge possible memory leak while cherry-picking.
On Mon, Aug 12, 2013 at 5:04 AM, Лежанкин Иван abys...@gmail.com 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 valgrind log? Or even better, a way to reproduce? Felipe, should I exclude you from my futher reports on possible memory leaks? Exclude me? -- Felipe Contreras -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huge possible memory leak while cherry-picking.
On Mon, Aug 12, 2013 at 5:04 AM, Лежанкин Иван abys...@gmail.com 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 valgrind log? Or even better, a way to reproduce? Felipe, should I exclude you from my futher reports on possible memory leaks? Exclude me? -- Felipe Contreras -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Huge possible memory leak while cherry-picking.
On Fri, Aug 9, 2013 at 7:13 AM, Лежанкин Иван abys...@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 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
