From: Dariqq <dariqq@posteo.net>
To: 74381@debbugs.gnu.org
Subject: bug#74381: High memory usage during guix pull (i686-linux, guile jit)
Date: Sat, 16 Nov 2024 12:58:14 +0000 [thread overview]
Message-ID: <3faad437-c87c-44d0-ad77-9e42418bf2dd@posteo.net> (raw)
Hi,
Using 'guix pull' on i686-linux regularly fails when building
'guix-packages-base':
E.g this recent run on ci.guix.gnu.org:
https://ci.guix.gnu.org/build/6472396/details
Log from me trying to pull 3e8d3d80f41e016cdfe80e488a78c2351c94fef8:
Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 8192 KiB
GC Warning: Failed to expand heap by 64 KiB
GC Warning: Out of Memory! Heap size: 3436 MiB. Returning NULL!
Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
[ 19/ 20] compiling... 90.0% of 10 filesallocating JIT code buffer
failed: Cannot allocate memory
JIT failed due to resource exhaustion
disabling automatic JIT compilation
allocate_stack failed: Cannot allocate memory
Warning: Unwind-only stack overflow exception; skipping pre-unwind handler.
[...]
The error suggests this might be related to guile jit compiling things
Disabling it by adding GUILE_JIT_THRESHOLD=-1 to the guix-daemon
environment got things working for me again.
reply other threads:[~2024-11-16 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3faad437-c87c-44d0-ad77-9e42418bf2dd@posteo.net \
--to=dariqq@posteo.net \
--cc=74381@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.