Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OOM when pulling Guix sources #1

Closed
raingloom opened this issue Aug 9, 2019 · 8 comments
Closed

OOM when pulling Guix sources #1

raingloom opened this issue Aug 9, 2019 · 8 comments

Comments

@raingloom
Copy link

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?

@raingloom
Copy link
Author

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% 

@oridb
Copy link
Owner

oridb commented Oct 19, 2019

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

@oridb
Copy link
Owner

oridb commented Oct 25, 2019

(Works for me, tentatively closing)

@oridb oridb closed this as completed Oct 25, 2019
@raingloom
Copy link
Author

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.

@raingloom
Copy link
Author

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% 

@raingloom
Copy link
Author

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

@raingloom
Copy link
Author

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

@oridb
Copy link
Owner

oridb commented Oct 29, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants