unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: 59365@debbugs.gnu.org
Cc: Romain Garbage <romain.garbage@inria.fr>,
	Greg Hogan <code@greghogan.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Marius Bakke <marius@gnu.org>
Subject: bug#59365: make-dynamic-linker-cache OOMs for LLVM 15 on i686-linux
Date: Fri, 12 Apr 2024 11:35:47 +0200	[thread overview]
Message-ID: <87le5igbyk.fsf@gnu.org> (raw)
In-Reply-To: <877cznidn8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 22 Nov 2022 09:42:19 +0100")

Hello,

Ludovic Courtès <ludo@gnu.org> skribis:

>>   GC Warning: Failed to expand heap by 285216768 bytes
>>   GC Warning: Failed to expand heap by 268439552 bytes
>>   GC Warning: Out of Memory! Heap size: 3620 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.
>>   Warning: Unwind-only out of memory exception; skipping pre-unwind handler.
>>
>> (excerpt from https://ci.guix.gnu.org/build/1702995/log/raw)
>>
>> Not sure why this phase uses so much memory.  Ideas?
>
> Yes: the gremlin.scm code uses ‘file-dynamic-info’, which loads the
> whole file in memory.  Ridiculous.
>
> We should instead mmap it (but there are no ‘mmap’ bindings in Guile,
> yet) or arrange to load just the relevant parts (we’ll have to check but
> maybe ‘file-dynamic-info’ can find everything it needs at the beginning
> of a file, the PT_DYNAMIC segment.)

Another instance of the problem that we just stumbled upon is ‘guix pack -RR’:
that too tries to load entire ELF files in memory, in
‘elf-loader-compile-flags’.

Mmap!

Ludo’.




      parent reply	other threads:[~2024-04-12  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 18:41 bug#59365: make-dynamic-linker-cache OOMs for LLVM 15 on i686-linux Marius Bakke
2022-11-22  8:42 ` Ludovic Courtès
2022-11-22 10:22   ` Maxim Cournoyer
2023-11-20 19:33     ` Maxim Cournoyer
2024-04-12  9:35   ` Ludovic Courtès [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87le5igbyk.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=59365@debbugs.gnu.org \
    --cc=code@greghogan.com \
    --cc=marius@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=romain.garbage@inria.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).