On Fri, Apr 02, 2010 at 09:54:14PM +0200, Frans Pop wrote:

quoted text
> I wanted to to a 'git gc' on my kernel repo, but that seemed to end in a 
> loop: loads of CPU usage, no output. Using 'ps' I found it's not 'git gc' 
> itself, but 'git reflog' that's causing the problem.
> 
> From the strace below it does seem like it still makes some progress, but 
> I've never had it take anywhere near this long before. Normally it starts 
> the count of objects almost immediately.
> 
> It's using hardly any memory at all but has one core going flat out.
> 
> I'm seeing this with both git 1.6.6.1 and 1.7.0.3 on the same repo.
> Environment:
> - Debian amd64/Lenny; Core Duo x86_64 2.6.34-rc3 -> 1.6.6.1
> - Debian i386/Sid; chroot on the same machine -> 1.7.0.3
> I've also tried with 2.6.33 to rule out a kernel issue.
> 
> Here's the tail end of an strace I ran. I broke it off after 9+ minutes, 
> but I had let it go for longer than that earlier. You can clearly see 
> where it starts to "stall" at 21:40:14.

FWIW, I have seen this, too, and managed to get an strace snippet that
looked similar to what you saw (mostly memory allocation, and otherwise
chewing on the CPU). I'm guessing there is some O(n^2) loop in there
somewhere. Unfortunately, mine actually completed after a few minutes
and I wasn't able to replicate.

Can you reproduce the problem on your repo? If so, can you possibly tar
it up and make it available (probably just the .git directory would be
enough)?

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html