From: swedebugia <swedebugia@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Danny Milosavljevic" <dannym@scratchpost.org>
Cc: 35660@debbugs.gnu.org
Subject: bug#35660: guix weather runaway memory consumption
Date: Wed, 15 May 2019 13:53:54 +0200 [thread overview]
Message-ID: <7cb8d719-ffe9-ccf1-e68e-936401869692@riseup.net> (raw)
In-Reply-To: <877easyd0w.fsf@gnu.org>
On 2019-05-14 22:52, Ludovic Courtès wrote:
> Hi Danny,
>
> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
>> The failure mode here is very very bad. Guix will consume all available
>> memory and then start on the swap, at which point the computer will
>> become unresponsive to any input and the user can't save any open
>> documents and has to kill the power to the computer.
>
> I agree that the failure mode is terrible. It’s very likely a cycle in
> the package graph, given the symptoms you describe. So ‘guix build
> OFFENDING-PACKAGE’ would probably give you the same result.
>
> Chris Baines proposed a patch a while back to detect and report cycles,
> but we never got around to polishing and integrating it. That would
> probably help a lot in these cases.
>
> We can open a new bug for that (if there’s not already one), but I think
> it should be framed in terms of cycle detection in the package graph and
> error reporting.
+1
When working on the NPM importer earlier this was very very common
happening with "guix build NPM-PACKAGE" because of cycles.
My strategy was to manually kill the build after a minute or two if no
output was produced.
--
Cheers Swedebugia
next prev parent reply other threads:[~2019-05-15 11:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 20:40 bug#35660: guix weather runaway memory consumption Danny Milosavljevic
2019-05-13 20:46 ` Ludovic Courtès
2019-05-13 21:25 ` Danny Milosavljevic
2019-05-14 20:52 ` Ludovic Courtès
2019-05-15 11:53 ` swedebugia [this message]
2021-08-18 1:03 ` Maxim Cournoyer
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=7cb8d719-ffe9-ccf1-e68e-936401869692@riseup.net \
--to=swedebugia@riseup.net \
--cc=35660@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=ludo@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.