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:23:54 +0100 Message-ID: <87turnyawl.fsf@gmail.com> References: <87k0slu13n.fsf@gmail.com> <87im84jsu0.fsf@gmail.com> <87h7nojsll.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="29284"; 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:25:35 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 1kyvKJ-0007Tu-2c for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jan 2021 12:25:35 +0100 Original-Received: from localhost ([::1]:36270 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kyvKI-0006vz-2x for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 11 Jan 2021 06:25:34 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46204) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kyvJo-0006vt-RY for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:25:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44327) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kyvJm-0003Sv-Mm for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:25:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kyvJm-0008SV-AO for bug-gnu-emacs@gnu.org; Mon, 11 Jan 2021 06:25: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:25: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.161036425032432 (code B ref 45751); Mon, 11 Jan 2021 11:25:02 +0000 Original-Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 11:24:10 +0000 Original-Received: from localhost ([127.0.0.1]:55873 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyvIv-0008R1-2O for submit@debbugs.gnu.org; Mon, 11 Jan 2021 06:24:09 -0500 Original-Received: from mail-pf1-f181.google.com ([209.85.210.181]:42126) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kyvIt-0008QZ-3S for 45751@debbugs.gnu.org; Mon, 11 Jan 2021 06:24:07 -0500 Original-Received: by mail-pf1-f181.google.com with SMTP id h10so10753077pfo.9 for <45751@debbugs.gnu.org>; Mon, 11 Jan 2021 03:24:07 -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=MQCY4CN8w+Yc/IKOLhAPPKtouLOof3Wrwi6+SunrSCk=; b=dcOOwzNWd6spsXEMF4JRvrG1wBeJGiMBKo1pO9CQkr7LhFwlKch4dEqRUh5sKwOKBT j400D5EbdJ8NDF8Xo6a61fOiZDgLamaiUzD2k4F5bZ4DMUCvLsmwKR0vCFQrzNff+Cg3 8fp3RqnulozE2lH8lRTemaPk/Un/Qsnpf8WTuXKUABa/6UUtzrsKzKLQowXiJMJJGh2U lfXNNx24gclh43C6TwgdM5nyfMsWt0iTaPeU1RTcKAFDW2odnqIWov62JEhUdH9Ygmql PdcjDn5n0aFUeoFuZFbXdrC80TDEmT4tN0hHAMm20QcHk8BCeW426zJvkT6BQWaEfo8n VCSw== 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=MQCY4CN8w+Yc/IKOLhAPPKtouLOof3Wrwi6+SunrSCk=; b=pGf5NhoWCjuZrXW8gT7U9qeLT3lfHp8grQe6Wbp704yMAjjmauIEKZ/07uksUiBvUD xEZmdm0YjtFOjpoz6kAq4ev2qWXiYsM2PGcxsI7/163P3zjgz/WQilkjPAbWKlFoK8t4 s+2EaFqW321VjVPTnBTpqDlAFKNJlfKG5f8KFvrB2gqc/EoMfdiOZG7X18nloohOctq0 1fPUz7GlyPJMmVxLbcSkq7mTqUJUlxhkbobRLx5Efgf8Yu8arUbumkr+gx7vFAImc/03 9Nw/q3rUYuXlkxI8wXudjO4HQy2onBDCBWSNAXR0KRfrxordPJQpo0YT4otfvnLOOGaP v0OA== X-Gm-Message-State: AOAM530OetdPLWRVx/33qmtCVSzRVpNj4//L6PnwbeHl570enqHbh+0e VWtwIwbs0JChLvg0wU1l+IGdgHU1J0A= X-Google-Smtp-Source: ABdhPJyYZkrVLq6yR4fiRdYkJXaWQBqY/yCUVDeujcAK+FvQqwY2+wXi53ISkkDXHteRFKLdxqhhFA== X-Received: by 2002:a65:458e:: with SMTP id o14mr19219308pgq.444.1610364241220; Mon, 11 Jan 2021 03:24:01 -0800 (PST) Original-Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14]) by smtp.gmail.com with ESMTPSA id n128sm19729938pga.55.2021.01.11.03.23.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Jan 2021 03:24:00 -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:197684 Archived-At: On lun., janv. 11 2021, Andrea Corallo wrote: > =C3=89douard Debry writes: > >> 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=20 >>>>> 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.= 603/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=20 >>> became >>> 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=20 >> some >> packages, some kind >> of blacklist. I would prefer at the moment because I am used to=20 >> this >> color theme. > > Yes, `comp-deferred-compilation-deny-list'. > Thanks ! In fact I just discovered this settings as you answered=20 me and (require 'comp) (setq comp-deferred-compilation-deny-list '("color-theme-*")) in my init file does the job. >> Do you think there may be a noticeable difference on emacs's >> performance between a >> color theme natively compiled (*eln) or just byte compiled=20 >> (*elc) > > I don't think so. > > Andrea