On Wed, Jun 13, 2012 at 11:27:04AM +0100, Thomas Lucas wrote:

> Hopefully this is the right place to send bug reports... The
> community page "http://git-scm.com/community"; suggests that it is.

It is the right place. Sorry that you did not get any response before

> During garbage collection (git gc) it encountered the following error:
> git gc | git gc --prune :
>    Counting objects: 856758, done.
>    Delta compression using up to 2 threads.
>    fatal: Out of memory, malloc failed (tried to allocate 303237121 bytes)
>    error: failed to run repack

Packing can be memory hungry if you have a lot of large objects (we may
hold several large objects in memory while comparing them for deltas).
It is also worse with 2 threads, as they will be working simultaneously,
but in the same memory space.

> The compression gets over 90% of the way through before this error
> occurs, but I don't think any compression results are kept, because
> when you repeat it has the same amount of work to do.

Right. Nothing is written during compression; we are just coming up with
a list of deltas to perform during the writing phase.

> My system is XP64 2 core with 4Gb of memory and plenty of virtual memory.

Unfortunately, I believe that the msysgit build is 32-bit, which means
you are probably not even getting to use all 4Gb of your address space
(my impression is that without special flags, 32-bit Windows processes
are limited to 2Gb of address space).

I'd first try doing the pack single-threaded by setting the pack.threads
config option to 1. If that doesn't work, you might try setting
pack.windowMemory to limit the delta search based on available memory
(usually it is limited by number of objects). If the large blobs are
ones that do not delta well anyway (e.g., compressed media files), you
might also consider setting the "-delta" attribute for them to skip
delta compression entirely.

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

Reply via email to