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 00:10:46 +0100 Message-ID: <87h7nojsll.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="39570"; 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 00:12:21 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 1kyjsj-000AD2-Eq for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jan 2021 00:12:21 +0100 Original-Received: from localhost ([::1]:50074 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kyjsi-00064J-DG for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 10 Jan 2021 18:12:20 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38704) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kyjsR-00063M-Ue for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 18:12:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43578) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kyjsP-00089N-SW for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 18:12:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kyjsP-0003vM-NN for bug-gnu-emacs@gnu.org; Sun, 10 Jan 2021 18:12:01 -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: Sun, 10 Jan 2021 23:12:01 +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.161032026114830 (code B ref 45751); Sun, 10 Jan 2021 23:12:01 +0000 Original-Received: (at 45751) by debbugs.gnu.org; 10 Jan 2021 23:11:01 +0000 Original-Received: from localhost ([127.0.0.1]:55124 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyjrR-0003r4-0O for submit@debbugs.gnu.org; Sun, 10 Jan 2021 18:11:01 -0500 Original-Received: from mail-pf1-f174.google.com ([209.85.210.174]:36991) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyjrP-0003qc-F3 for 45751@debbugs.gnu.org; Sun, 10 Jan 2021 18:10:59 -0500 Original-Received: by mail-pf1-f174.google.com with SMTP id 11so9881153pfu.4 for <45751@debbugs.gnu.org>; Sun, 10 Jan 2021 15:10:59 -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=g3ws5G0QDtZk9f7awg0XI/5ClzZhOFxO+Q2whpiiThQ=; b=Yzke0Z8EKLHnH50xTtKmkhSs6yerYZFl9sdGl/FwOCRxerxuuj9c1VdRPO5P6UTvAu E2r+ZuEgARpY09jqcVBb3qDNMs3KNDHT0pMNt9v2BQBNkuspKgrVX7+VYEZOITt5HUia 7opRJm5fgvUAiYBb+3qMhAUcbDLWP984FFEYFGjZrPvh6FGI0UI0Frxyb8op9JJu3ZzF 3Kse1M8E1Jd4gFQQifpMzfBdAwescbmzLpGXNhEpXInsvVOGBJ/ms9kndMguq1EB50f1 T7pnHbtpkm291llA3khClG00IrHhYEUEbYbmKfAuNMv8kMbYdBHV0d1iwmUhGfQwA5q6 vsDA== 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=g3ws5G0QDtZk9f7awg0XI/5ClzZhOFxO+Q2whpiiThQ=; b=iXV4MgWa/EdRGngRkBQaYxVRkbVKnUDOE0nT/k2jCwMWzjmxUuAvcLVBbD+/EeouXF d55yOPxO/d7qRQVXF50RyyPk3fO0Dl9t8LN0xSQcQ2v3g/BxnE8sZ0degjAd5lN8U6u/ 3fUcwAuJ5LQtm62Y3lCS1PTk2IoMsqM0S/lMyNVoe0zR6Lv3tUaXWy/EI4GYjqIZz7GE 0G+B3RdMGV/TmvCnrrKFFb/6fRGigV9Ww0IVZlYMu0eFSwynWQ3cGZKVt4YMs3fo/tNy afl6RIVSq7hyFBo/UpJ5P8aquRJJIy5KEcAzXf/EUCwunv8cpS2iKxAIkJBCNoXxwFBg gp0g== X-Gm-Message-State: AOAM5307JOSOLCGgAqBJggJy0KmRhYymZozUIAWpScp19L8caqGp7dTV u00pmHC+OYKf6xFp1JCXMgYxDCIvNBQ= X-Google-Smtp-Source: ABdhPJyWZn2V6l/HG7W3fRFcl9rCH39fqpiGwqIM+2rSBZDDx1NcPnIrTMau1ykXnSoOnYdGs2piGQ== X-Received: by 2002:a63:4d59:: with SMTP id n25mr16842691pgl.122.1610320253724; Sun, 10 Jan 2021 15:10:53 -0800 (PST) Original-Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14]) by smtp.gmail.com with ESMTPSA id a141sm16782181pfa.189.2021.01.10.15.10.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 10 Jan 2021 15:10:53 -0800 (PST) In-reply-to: <87im84jsu0.fsf@gmail.com> 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:197669 Archived-At: On lun., janv. 11 2021, =C3=89douard Debry wrote: > 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 eat=20 >>> 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.60= 3/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 guess=20 >> 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 cases,=20 >> 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=20 > totally unresponsive, I > had to reboot. > > I am not 100% sure it is because of emacs compiling the color=20 > theme package and eating > all memory, > but I never had such a crash on linux since I own this laptop=20 > and I had exactly the same > crash on > windows 10 with emacs native-comp eating all memory. > > So most probably, my previous bug is related to that. I could=20 > try another theme and see > if this still happens. > > Regards Also, is there a way to prevent emacs native-comp to compile some=20 packages, some kind of blacklist. I would prefer at the moment because I am used to=20 this color theme. Do you think there may be a noticeable difference on emacs's=20 performance between a color theme natively compiled (*eln) or just byte compiled (*elc) Regards