From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: bug#35660: guix weather runaway memory consumption Date: Wed, 15 May 2019 13:53:54 +0200 Message-ID: <7cb8d719-ffe9-ccf1-e68e-936401869692@riseup.net> References: <20190509224044.60b37e3f@scratchpost.org> <87ftpiozfl.fsf@gnu.org> <20190513232558.22b4afc0@scratchpost.org> <877easyd0w.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQsS4-0003RF-Ny for bug-guix@gnu.org; Wed, 15 May 2019 07:52:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hQsS3-0000cH-In for bug-guix@gnu.org; Wed, 15 May 2019 07:52:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:37750) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hQsS2-0000av-2m for bug-guix@gnu.org; Wed, 15 May 2019 07:52:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hQsS2-0004LS-03 for bug-guix@gnu.org; Wed, 15 May 2019 07:52:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <877easyd0w.fsf@gnu.org> Content-Language: en-US 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Danny Milosavljevic Cc: 35660@debbugs.gnu.org On 2019-05-14 22:52, Ludovic Courtès wrote: > 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’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