Steven Grimm <koreth@xxxxxxxxxxxxx> wrote: > FYI, with this patch, it actually dies more often. The stack seems to be > corrupted so I can't give you a useful stack trace, but here's what gdb > says: Yikes. Thanks for the feedback. Sorry, I've still been busy with another big project and haven't been able to track down this nasty bug. If somebody wants to take a stab at working around it: hack up a patch that forks a new child (reusing the main connection) for every revision it needs to fetch. It should still be as fast as normal on *nix machines because fork() is fast and it won't have to renegotiate the connection in every child, but memory leaks and corruption won't have a chance to accumulate. -- Eric Wong - 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