From: Julien Lepiller <julien@lepiller.eu>
To: 48963@debbugs.gnu.org
Subject: bug#48963: "guix build guix" halts after exhausting memory
Date: Sat, 12 Jun 2021 00:23:30 +0200 [thread overview]
Message-ID: <20210612002330.64cd06c1@tachikoma.lepiller.eu> (raw)
Hi Guix!
I tried updating my system on my armhf board (2GB of RAM), but during
"guix system reconfigure", guix tries to build itself (the guix package
from (gnu packages package-management)). This package uses too much
memory to build, and I start getting GC warnings like so:
GC Warning: Out of memory - trying to allocate requested amount (552
bytes)...
GC Warning: Header allocation failed: dropping block
GC Warning: Out of Memory! Heap size: 2571 MiB. Returning NULL!
Warning: Unwind-only out of memory exception; skipping pre-unwind
handler.
after some more progress and a lot more warnings, the build stops (CPU
is at 2%), but the memory is not freed. The build stayed stuck for a
long time until I decided to cancel it.
As a work-around, I tried using the guix-daemon package instead (by
changing the guix field in guix-configuration), but "guix system" still
wants to build the guix package anyway. I tried finding usages of the
guix package (grepping for "package-management" yields a relatively
short list of files, and none of them seems to be used by my config,
except (gnu services base) which always uses the guix from the
configuration). Why?
Can we instead break the build (at the Makefile level) into multiple
smaller chunks, that require less memory, in the same way (guix self)
works?
next reply other threads:[~2021-06-11 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 22:23 Julien Lepiller [this message]
2021-06-11 22:30 ` bug#48963: "guix build guix" halts after exhausting memory Julien Lepiller
2021-06-16 20:01 ` Ludovic Courtès
2021-06-17 13:58 ` Julien Lepiller
2021-06-17 22:17 ` Julien Lepiller
2021-06-18 9:51 ` Ludovic Courtès
2021-06-18 10:52 ` Julien Lepiller
2021-06-20 21:00 ` Ludovic Courtès
2021-06-21 11:05 ` Julien Lepiller
2021-06-23 21:43 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210612002330.64cd06c1@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=48963@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.