GNU bug report logs - #35660
guix weather runaway memory consumption

Previous Next

Full log

View this message in rfc822 format

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: swedebugia <swedebugia <at> riseup.net>
Cc: Danny Milosavljevic <dannym <at> scratchpost.org>, Ludovic Courtès <ludo <at> gnu.org>, 35660 <at> debbugs.gnu.org
Subject: bug#35660: guix weather runaway memory consumption
Date: Tue, 17 Aug 2021 21:03:48 -0400

retitle 35660 Implement cycle detection with proper reporting
thanks

swedebugia <swedebugia <at> riseup.net> writes:

> On 2019-05-14 22:52, Ludovic Courtès wrote:
>> Hi Danny,
>> Danny Milosavljevic <dannym <at> 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

This would indeed be very useful.  I'm retitling this bug so that it is
more actionable.  Could someone link to the patch Chris Baines had
written going in this direction?

Thanks,

Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.