From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=C3=89douard?= Debry Newsgroups: gmane.emacs.bugs Subject: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU Date: Mon, 11 Jan 2021 12:25:56 +0100 Message-ID: <87sg77yat7.fsf@gmail.com> References: <87k0slu13n.fsf@gmail.com> <87im84jsu0.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36602"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.0; emacs 28.0.50 Cc: 45751@debbugs.gnu.org To: Andrea Corallo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 11 12:27:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kyvLq-0009QA-Qx for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jan 2021 12:27:10 +0100 Original-Received: from localhost ([::1]:37910 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kyvLp-0007mk-S0 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jan 2021 06:27:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46798) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kyvLi-0007mP-Jz for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:27:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44343) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kyvLi-0004Tf-CU for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kyvLi-0000EO-82 for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=C3=89douard?= Debry Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 11 Jan 2021 11:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45751 X-GNU-PR-Package: emacs Original-Received: via spool by 45751-submit@debbugs.gnu.org id=B45751.1610364371821 (code B ref 45751); Mon, 11 Jan 2021 11:27:02 +0000 Original-Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 11:26:11 +0000 Original-Received: from localhost ([127.0.0.1]:55889 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyvKt-0000DB-3Z for submit@debbugs.gnu.org; Mon, 11 Jan 2021 06:26:11 -0500 Original-Received: from mail-pl1-f175.google.com ([209.85.214.175]:45891) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyvKr-0000Cv-BB for 45751@debbugs.gnu.org; Mon, 11 Jan 2021 06:26:09 -0500 Original-Received: by mail-pl1-f175.google.com with SMTP id e2so9326692plt.12 for <45751@debbugs.gnu.org>; Mon, 11 Jan 2021 03:26:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version:content-transfer-encoding; bh=Vm6V5lF8c+mPJJpZSUYh88wMn6DMgi+qanXgztuLK2g=; b=ZNkUvnXmJSWT7ekCJzrMIR0JkeWMUVylQcQkIl/Sgv+WiaDi773d3UwOh+npcFfxa3 y+zAVs4mlRiKZ9SjWeHoMXHrI+ivRqfUx0K3QfPoZv2Q+YogwSPrrcnIczneENTpekRz Zx1+tt0eRdpt7mdYlFi5MRSMyh6qawwesb6NqylbkKSh+axJwEBixmkaI1MWxwbbtw47 IB69yjrW1ZOQ/zlBO1B+nTGCMjTOeGDe/3BLijAC7VNiOOX68cwDVCDDxwknove88G+I tFeqw7fnJDYZuuS0JIO0He6ITHr3vPr3yfmGaoSDk35CZH3L4fU9oDDeAI5QRMvJLIgI LxUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version:content-transfer-encoding; bh=Vm6V5lF8c+mPJJpZSUYh88wMn6DMgi+qanXgztuLK2g=; b=PwL2T/gibFzMXtwsTokfoyaVXB7G/gTE84ZLLCl1vQjTI3wpo8gyDZyAOG+t6Hp6OB 7qAnBY5fGrMqCrxhR3HyZ8dZyf4ouVL7X62atsEm/PERFdxytV6opEh4t5T9jkCl7lBF 3n6loLYcgoGoO9mcwvIfyiCHkp8L/ULmzeeWZp5Q2H2LoERRYka75QpU9Ou5jwwNEnCC b1vINiPfB41cGYMYAxE1rKUEQfE6K9e6HHMjkhhGqJCD068N9ySm5vv+MNjArdgwCkYv Xrj/DOOnGIk5A+FteHd++Iy1HCVxbj0Ik/yugr1OskXm7iPjYcl9G8bWnDwspXIJ4cJF vUuQ== X-Gm-Message-State: AOAM532FLffjOKmHL3QQt/VsJO2RWeCYrw+nN6fMaaZtJqPo6fX/tuGz a79dY9jjKdAu6bj10GsDWeUqGibePBY= X-Google-Smtp-Source: ABdhPJy1wdgaQZ4FGSeLy6DyLH3gMBv6j/p5qq/TIl+PmPc+39dtM3ohIM44EUVhXV4CidoFxrvJzw== X-Received: by 2002:a17:90a:e551:: with SMTP id ei17mr17169718pjb.187.1610364363449; Mon, 11 Jan 2021 03:26:03 -0800 (PST) Original-Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14]) by smtp.gmail.com with ESMTPSA id x15sm17933236pfn.118.2021.01.11.03.26.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Jan 2021 03:26:02 -0800 (PST) In-reply-to: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:197686 Archived-At: On lun., janv. 11 2021, Andrea Corallo wrote: > =C3=89douard Debry writes: > >> On dim., janv. 10 2021, Andrea Corallo wrote: >>> =C3=89douard Debry writes: >>> >>>> I noticed that when launching emacs on linux (debian buster), >>>> it keeps on running 100% of the CPU and seems to gradually=20 >>>> eat all >>>> memory, approximately 1-2% every minute. >>>> >>>> It seems related to native compiling. In the >>>> *Async-native-compile-log* I read : >>>> >>>> <=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D> >>>> Compiling >>>> /home/edouard/.emacs.d/elpa/color-theme-sanityinc-solarized-20200805.6= 03/color-theme-sanityinc-solarized.el... >>> >>> I see a similar issue with sanityinc-tomorrow.el, the=20 >>> compilation is >>> way >>> slower than any other one but it completes eventually. I=20 >>> guess is >>> the >>> same issue you see and with sufficient RAM also=20 >>> sanityinc-solarized >>> should complete. >>> >>> In case of of sanityinc-tomorrow I think is because of >>> `color-theme-sanityinc-tomorrow'. This is a single function=20 >>> that >>> after >>> macro expansion becomes enormous. >>> >>> We need to make the compiler robust against these corner=20 >>> cases, I'll >>> have a look this week into adding some logic for that. >>> >>> Thanks >>> >>> Andrea >> >> I have waited for approximately one hour and until linux became >> totally unresponsive, I had to reboot. > > Right, these are the classical symptoms of a system swapping for > insufficient physical memory (or excessive mem usage by a=20 > program :) Probably, my previous bug report "Excessive memory ..." was due to=20 this package trying to be natively compiled. I will try the=20 "comp-deferred-compilation-deny-list" setting on windows 10 so as to be sure there is nothing more. Regards