I keep having git-repack run out of virtual memory ( 32 bit system )
when trying to repack my linux kernel repo. It keeps making it right up
to 99% then barfing saying mmap failed: Cannot allocate memory.
I thought I could help this by limiting the pack size, and using
--window-memory to
On 6/1/2015 2:43 PM, Junio C Hamano wrote:
Phil Susi ps...@ubuntu.com writes:
I keep having git-repack run out of virtual memory ( 32 bit system )
when trying to repack my linux kernel repo. It keeps making it right
up to 99% then barfing saying mmap failed: Cannot allocate memory.
I thought
Phil Susi ps...@ubuntu.com writes:
I keep having git-repack run out of virtual memory ( 32 bit system )
when trying to repack my linux kernel repo. It keeps making it right
up to 99% then barfing saying mmap failed: Cannot allocate memory.
I thought I could help this by limiting the pack
On Mon, Jun 01, 2015 at 03:07:16PM -0400, Phil Susi wrote:
It's more the --window-memory argument that is important here: it is
supposed to prevent exactly this problem. I guess I tried adding the
--max-pack-size as well on the off chance that it would help.
How many processors do you have?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/01/2015 04:58 PM, Jeff King wrote:
How many processors do you have? The window-memory is per-thread.
Try with --threads=1.
Ahh, right... 8... that explains it ;)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
5 matches
Mail list logo
