Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

2016-10-21 Thread Ian Jackson
Control: reassign -1 dgit-infrastructure Control: found -1 2.4 Control: retitle -1 Should occasionally run git-gc in dgit-repos Anders Kaseorg writes ("Re: Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory""): > On Thu, 20 Oct 2016, Ian Jackson wr

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

2016-10-20 Thread Anders Kaseorg
On Thu, 20 Oct 2016, Ian Jackson wrote: > Does that seem right ? Sounds right to me. > I have an outstanding question: do I need to lock against concurrent > updates by other programs ? That is, can I run git-gc and (say) > git-receive-pack at the same time, safely ? This is safe by default,

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

2016-10-20 Thread Ian Jackson
Anders Kaseorg writes ("Re: Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory""): > Git really is running out of memory. When I try this locally (using > file:// to force Git to go through the same git-upload-pack dance that it > does over

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

2016-10-20 Thread Anders Kaseorg
Git really is running out of memory. When I try this locally (using file:// to force Git to go through the same git-upload-pack dance that it does over a smart transport, and using ulimit -v as a poor but probably sufficient approximation of a RAM-limited server), it fails with 920 MB of

Bug#841414: git "fatal: Out of memory? mmap failed: Cannot allocate memory"

2016-10-20 Thread Ian Jackson
Control: reassign -1 git Control: found -1 1:2.1.4-2.1+deb8u2 Hi, git maintainers. I'm having a bit of a conundrum with the dgit git server and I hope you can help. I don't know that this is a bug in git. I'm reassigning this bug to git so as to ask for your input, and I expect that after we