On Thu, Aug 05, 2010 at 08:33:02AM +0200, Ivan Kanis wrote: > I am ready to do whatever to diagnose the problem. I know C pretty well > and am ready to look into it but I am not sure where to start. It sounds like Git is reading each object into memory to send it to the client, but doesn't remember to free the memory at the end of sending the object, so it remains as a memory leak. I would look in the code for malloc calls that don't have a free call, or spots where free calls might not be hit. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html