OOM when pulling Guix sources

Question

OOM when pulling Guix sources

Closed this issue 5 years ago · 8 comments

cpu% git/clone 'git://git.savannah.gnu.org/guix.git'
fetching...
indexing (0/288594):......................fetch 2966: Killed: Insufficient physical memory
clone failed.
cleaning up guix

Is this expected?

Answer 1 · 2019-08-10T00:48:34.000Z

after adding a few gigs of swap:

cpu% git/clone 'git://git.savannah.gnu.org/guix.git'
fetching...
indexing (0/288594):...............................git/fetch: malloc: segments overlap
clone failed.
cleaning up guix
cpu%

Answer 2 · 2019-10-19T14:33:09.000Z

Is this still a problem for you? (lots of changes and efficiency improvements since this was posted)

Answer 3 · 2019-10-25T02:41:05.000Z

(Works for me, tentatively closing)

Answer 4 · 2019-10-28T11:23:33.000Z

My CPU server was down so I couldn't test it, I'm trying to clone it again, but if it worked for you, it's probably fixed.

Answer 5 · 2019-10-28T12:01:47.000Z

Still getting this error with swap enabled:

cpu% git/clone 'git://git.savannah.gnu.org/guix.git'
fetching...
indexing (0/299424):.................................git/fetch: malloc: segments overlap
cpu%

Answer 6 · 2019-10-28T12:02:23.000Z

Might be a bug in malloc though, maybe an overflow?

Answer 7 · 2019-10-28T12:03:40.000Z

The system is a Raspberry Pi 3 B+, running a (slightly outdated, but only by a few months) 32 bit kernel.

Answer 8 · 2019-10-29T01:27:40.000Z

That message means it's definitely running out of memory (segments overlap means that the heap has grown to meet the stack). I'm a bit surprised, but I guess it's plausible. Try dropping Cachemax in git.h to maybe, 512, and report back?

If not, maybe turn the out of memory in malloc into an abort so you can run leak on the broken proc. guix doesn't seem like it's particuarly big, so I'm not sure what would be taking all that memory.