From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#35660: guix weather runaway memory consumption Date: Tue, 14 May 2019 22:52:31 +0200 Message-ID: <877easyd0w.fsf@gnu.org> References: <20190509224044.60b37e3f@scratchpost.org> <87ftpiozfl.fsf@gnu.org> <20190513232558.22b4afc0@scratchpost.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:38829) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQeUi-0007X1-ST for bug-guix@gnu.org; Tue, 14 May 2019 16:57:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hQeQ3-0007x5-MW for bug-guix@gnu.org; Tue, 14 May 2019 16:53:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36462) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hQeQ2-0007uL-5K for bug-guix@gnu.org; Tue, 14 May 2019 16:53:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hQeQ2-00058c-26 for bug-guix@gnu.org; Tue, 14 May 2019 16:53:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190513232558.22b4afc0@scratchpost.org> (Danny Milosavljevic's message of "Mon, 13 May 2019 23:25:58 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Danny Milosavljevic Cc: 35660@debbugs.gnu.org Hi Danny, Danny Milosavljevic 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=E2=80=99s very likely a cycl= e in the package graph, given the symptoms you describe. So =E2=80=98guix build OFFENDING-PACKAGE=E2=80=99 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=E2=80=99s not already one), but I = think it should be framed in terms of cycle detection in the package graph and error reporting. Thanks, Ludo=E2=80=99.