GNU bug report logs - #45751
[feature/native-comp] emacs keeps running 100% of CPU

Please note: This is a static page, with minimal formatting, updated once a day.
Click here to see this page with the latest information and nicer formatting.

Package: emacs; Reported by: Édouard Debry <edouard.debry@HIDDEN>; merged with #45705; dated Sat, 9 Jan 2021 23:45:02 UTC; Maintainer for emacs is bug-gnu-emacs@HIDDEN.
Merged 45705 45751. Request was from Andrea Corallo <akrl@HIDDEN> to control <at> debbugs.gnu.org. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 12 Jan 2021 10:57:04 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Tue Jan 12 05:57:04 2021
Received: from localhost ([127.0.0.1]:59425 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kzHMF-0007ch-O8
	for submit <at> debbugs.gnu.org; Tue, 12 Jan 2021 05:57:03 -0500
Received: from mx.sdf.org ([205.166.94.24]:52704)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kzHMA-0007cF-7y
 for 45751 <at> debbugs.gnu.org; Tue, 12 Jan 2021 05:57:01 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10CAuu0D005403;
 Tue, 12 Jan 2021 10:56:57 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: edouard debry <edouard.debry@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <xjfy2gzg4of.fsf@HIDDEN>
 <87sg77yat7.fsf@HIDDEN> <xjfczybfs12.fsf@HIDDEN>
 <CAMJA--b63GWDcNZfxFG7gHVBuFGoDWOCzXU88+Ps8xOEOx4-FA@HIDDEN>
Date: Tue, 12 Jan 2021 10:56:56 +0000
In-Reply-To: <CAMJA--b63GWDcNZfxFG7gHVBuFGoDWOCzXU88+Ps8xOEOx4-FA@HIDDEN>
 (edouard debry's message of "Tue, 12 Jan 2021 11:00:01 +0100")
Message-ID: <xjfim82e83r.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

edouard debry <edouard.debry@HIDDEN> writes:

> Tried on windows.
>
> Indeed, with previous settings in my init file, I do not see anymore emacs eating all memory, currently it remains at
> ~150Mo while idle.

Right so I'll merge with bug#45705.

> The only trouble is that some packages fail to be natively compiled as "smart-mode-line" with the same error :
> Debugger entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2) 
>
> I blacklisted this package too.
>
> Details of the error follows, I presume this is a compatibility problem with emacs 28.0.50 ?

Yes I think so.

  Andrea




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 12 Jan 2021 10:00:23 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Tue Jan 12 05:00:23 2021
Received: from localhost ([127.0.0.1]:59346 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kzGTO-0005oo-Q3
	for submit <at> debbugs.gnu.org; Tue, 12 Jan 2021 05:00:23 -0500
Received: from mail-ej1-f53.google.com ([209.85.218.53]:34490)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kzGTL-0005oT-Ax
 for 45751 <at> debbugs.gnu.org; Tue, 12 Jan 2021 05:00:21 -0500
Received: by mail-ej1-f53.google.com with SMTP id g20so2677245ejb.1
 for <45751 <at> debbugs.gnu.org>; Tue, 12 Jan 2021 02:00:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=zAfWXcU4cZ3rpgkJCaRcs7yPOEciS/y7Frc8ruFqRDE=;
 b=DC23Rpvz702gEulBwKv3tUDJVMxiKhTY6Iw+ZBB34+z1l7zYaY8deRvWpPwc9Zjrsm
 kXjfK/8zY4oXoXHcYPCWsSO8yJa/QVhR3I9ma9sZH35wgAPhPHKSTfZlKutrkiKxZ5Ph
 4CaFruf4MC7iFxyMjuXIWq7PQH3ewQ4rBv32ErZEUSSYzFjCNNqPkxkNT+zHeH4kxXTo
 8llzWiEBo1H3uoj2JLq4UoaUs8wYa9YpxXHmQRIgMOUr317lrcD4cCI/Onl6Oc+pYi/E
 R10xEsfNZcZReBiwVv0muu4dPVXbn8ze9WCtwZxR20aI2uaiF0dndw2uq3PVx2z+WY+t
 FS1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=zAfWXcU4cZ3rpgkJCaRcs7yPOEciS/y7Frc8ruFqRDE=;
 b=aQBAdbVDCcWzoVTK6D+eq43MQvIOp2LurRGuRCNo+jKrRJ8AULO9viERff45/MKYZD
 gHuYLmnWNWfqaKnAGdGYAZps8uNEfY+udtGsiLFHqTIwqrDeJSuelQjBMJUGn9xH6Yzi
 QsZ0BJ0n7UohGciVZ+WFkqwIqIvepNoBTioFKG+I2GraK2joogVjf26bYFLeL01lIaAU
 P4nqGKHh7Q9qMPjJNl4Qw4M0udLog44zbult4sAsDX2g+ZIFHLvpVbzCy8cBU7zQvC8D
 c7YIRBJvSwA8Wwa/+ycjc8Ng3HmdbR0tT/KUGbNu1dYIL0VamRerbMmH6BvODiWVeS/O
 IFWA==
X-Gm-Message-State: AOAM530FlvlvV2tK+GNAEziBIKW39OpgcYzEf91O9e3z/uB9NMg4Ga0l
 UCM4ksrCzqM+u1xVnQ0axaEE7P4LWDyy8srRqPo=
X-Google-Smtp-Source: ABdhPJxpVJBW4Poh6s2xDElrdmgYREm9goeZOgF+iUsrJcGGwOaWsLhiu43ZjBMq3BY2JBYqu0qOdNODzzEP/iiBVYE=
X-Received: by 2002:a17:906:2e16:: with SMTP id
 n22mr2695931eji.477.1610445613248; 
 Tue, 12 Jan 2021 02:00:13 -0800 (PST)
MIME-Version: 1.0
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <xjfy2gzg4of.fsf@HIDDEN>
 <87sg77yat7.fsf@HIDDEN> <xjfczybfs12.fsf@HIDDEN>
In-Reply-To: <xjfczybfs12.fsf@HIDDEN>
From: edouard debry <edouard.debry@HIDDEN>
Date: Tue, 12 Jan 2021 11:00:01 +0100
Message-ID: <CAMJA--b63GWDcNZfxFG7gHVBuFGoDWOCzXU88+Ps8xOEOx4-FA@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
To: Andrea Corallo <akrl@HIDDEN>
Content-Type: multipart/alternative; boundary="000000000000b5352d05b8b116af"
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

--000000000000b5352d05b8b116af
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Tried on windows.

Indeed, with previous settings in my init file, I do not see anymore emacs
eating all memory, currently it remains at ~150Mo while idle.

The only trouble is that some packages fail to be natively compiled as
"smart-mode-line" with the same error :
Debugger entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2)

I blacklisted this package too.

Details of the error follows, I presume this is a compatibility problem
with emacs 28.0.50 ?

Regards

<=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D>
Compiling
c:/Users/xxx/.emacs.d/elpa/smart-mode-line-20190527.1156/smart-mode-line.el=
...
Debugger entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2)
  #f(compiled-function (obsolete-name current-name when &optional
docstring) "Make OBSOLETE-NAME a variable alias for CURRENT-NAME and mark
it obsolete.\n\nWHEN should be a string indicating when the variable was
first\nmade obsolete, for example a date or a release number.\n\nThis macro
evaluates all its parameters, and both OBSOLETE-NAME\nand CURRENT-NAME
should be symbols, so a typical usage would look like:\n\n
 (define-obsolete-variable-alias 'foo-thing 'bar-thing \"27.1\")\n\nThis
macro uses `defvaralias' and `make-obsolete-variable' (which see).\nSee the
Info node `(elisp)Variable Aliases' for more details.\n\nIf CURRENT-NAME is
a defcustom or a defvar (more generally, any variable\nwhere OBSOLETE-NAME
may be set, e.g. in an init file, before the\nalias is defined), then the
define-obsolete-variable-alias\nstatement should be evaluated before the
defcustom, if user\ncustomizations are to be respected.  The simplest way
to achieve\nthis is to place the alias statement before the defcustom
(this\nis not necessary for aliases that are autoloaded, or in
files\ndumped with Emacs).  This is so that any user customizations
are\napplied before the defcustom tries to initialize the\nvariable (this
is due to the way `defvaralias' works).\n\nFor the benefit of Customize, if
OBSOLETE-NAME has\nany of the following properties, they are copied
to\nCURRENT-NAME, if it does not already have them:\n`saved-value',
`saved-variable-comment'." #<bytecode 0x127e504c6e942a72>)('sml/time-format
'display-time-format)
  macroexpand((define-obsolete-variable-alias 'sml/time-format
'display-time-format) ((sml/-debug . #f(compiled-function (fmt &rest r)
#<bytecode -0x528c1381ccb3bab>)) (declare-function .
byte-compile-macroexpand-declare-function) (eval-when-compile .
#f(compiled-function (&rest body) #<bytecode -0xcee878b9e5c479>))
(eval-and-compile . #f(compiled-function (&rest body) #<bytecode
0x31ea4933231cd9b>)) (with-suppressed-warnings . #f(compiled-function
(warnings &rest body) #<bytecode 0x11867883d853666e>))))
  macroexp-macroexpand((define-obsolete-variable-alias 'sml/time-format
'display-time-format) ((sml/-debug . #f(compiled-function (fmt &rest r)
#<bytecode -0x528c1381ccb3bab>)) (declare-function .
byte-compile-macroexpand-declare-function) (eval-when-compile .
#f(compiled-function (&rest body) #<bytecode -0xcee878b9e5c479>))
(eval-and-compile . #f(compiled-function (&rest body) #<bytecode
0x31ea4933231cd9b>)) (with-suppressed-warnings . #f(compiled-function
(warnings &rest body) #<bytecode 0x11867883d853666e>))))
  byte-compile-recurse-toplevel((define-obsolete-variable-alias
'sml/time-format 'display-time-format) #<subr
F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_45>)
  byte-compile-toplevel-file-form((define-obsolete-variable-alias
'sml/time-format 'display-time-format))
  #<subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_43>(#<buffer
 *Compiler Input*>)
  byte-compile-from-buffer(#<buffer  *Compiler Input*>)
  byte-compile-file("c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...")
  #f(compiled-function (filename) "Byte-compile FILENAME spilling data from
the byte compiler." #<bytecode
0x8fb180dc298647e>)("c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...")
  apply(#f(compiled-function (filename) "Byte-compile FILENAME spilling
data from the byte compiler." #<bytecode 0x8fb180dc298647e>)
"c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019..." nil)

comp-spill-lap-function("c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...=
")
  comp-spill-lap("c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...")
  #f(compiled-function (pass) #<bytecode
0x1a1ac110a850427c>)(comp-spill-lap)
  mapc(#f(compiled-function (pass) #<bytecode 0x1a1ac110a850427c>)
(comp-spill-lap comp-limplify comp-fwprop comp-call-optim comp-ipa-pure
comp-add-cstrs comp-fwprop comp-dead-code comp-tco comp-fwprop
comp-remove-type-hints comp-final))
  comp--native-compile("c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019..."
t)

load-with-code-conversion("c:/Users/xxx/AppData/Local/Temp/emacs-async-com.=
.."
"c:/Users/xxx/AppData/Local/Temp/emacs-async-com..." nil t)
  command-line-1(("-l"
"c:/Users/xxx/AppData/Local/Temp/emacs-async-com..."))
  command-line()
  normal-top-level()
<=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D>



Le lun. 11 janv. 2021 =C3=A0 15:48, Andrea Corallo <akrl@HIDDEN> a =C3=A9c=
rit :

> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>
> > On lun., janv. 11 2021, Andrea Corallo wrote:
> >> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
> >>
> >>> On dim., janv. 10 2021, Andrea Corallo wrote:
> >>>> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
> >>>>
> >>>>> I noticed that when launching emacs on linux (debian buster),
> >>>>> it keeps on running 100% of the CPU and seems to gradually 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 compilation
> >>>> is
> >>>> way
> >>>> slower than any other one but it completes eventually.  I guess is
> >>>> the
> >>>> same issue you see and with sufficient RAM also
> >>>> sanityinc-solarized
> >>>> should complete.
> >>>>
> >>>> In case of of sanityinc-tomorrow I think is because of
> >>>> `color-theme-sanityinc-tomorrow'.  This is a single function that
> >>>> after
> >>>> macro expansion becomes enormous.
> >>>>
> >>>> We need to make the compiler robust against these corner 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 program :)
> >
> > Probably, my previous bug report "Excessive memory ..." was due to
> > this package
> > trying to be natively compiled. I will try the
> > "comp-deferred-compilation-deny-list"
> > setting on windows 10 so as to be sure there is nothing more.
>
> Thanks, let us know so in case we can close the duplicate.
>
>   Andrea
>

--000000000000b5352d05b8b116af
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Tried on windows.</div><div><br></div><div>Indeed, wi=
th previous settings in my init file, I do not see anymore emacs eating all=
 memory, currently it remains at ~150Mo while idle.</div><div><br></div><di=
v>The only trouble is that some packages fail to be natively compiled as &q=
uot;smart-mode-line&quot; with the same error :</div><div>
Debugger entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2) <br></d=
iv><div><br></div><div>I blacklisted this package too.<br></div><div><br></=
div><div>Details of the error follows, I presume this is a compatibility pr=
oblem with emacs 28.0.50 ?</div><div><br></div><div>Regards<br></div><div><=
br></div><div>&lt;=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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D&gt;<br></div><div>Compiling c:/Users/xxx/=
.emacs.d/elpa/smart-mode-line-20190527.1156/smart-mode-line.el...<br>Debugg=
er entered--Lisp error: (wrong-number-of-arguments (3 . 4) 2)<br>=C2=A0 #f(=
compiled-function (obsolete-name current-name when &amp;optional docstring)=
 &quot;Make OBSOLETE-NAME a variable alias for CURRENT-NAME and mark it obs=
olete.\n\nWHEN should be a string indicating when the variable was first\nm=
ade obsolete, for example a date or a release number.\n\nThis macro evaluat=
es all its parameters, and both OBSOLETE-NAME\nand CURRENT-NAME should be s=
ymbols, so a typical usage would look like:\n\n =C2=A0(define-obsolete-vari=
able-alias &#39;foo-thing &#39;bar-thing \&quot;27.1\&quot;)\n\nThis macro =
uses `defvaralias&#39; and `make-obsolete-variable&#39; (which see).\nSee t=
he Info node `(elisp)Variable Aliases&#39; for more details.\n\nIf CURRENT-=
NAME is a defcustom or a defvar (more generally, any variable\nwhere OBSOLE=
TE-NAME may be set, e.g. in an init file, before the\nalias is defined), th=
en the define-obsolete-variable-alias\nstatement should be evaluated before=
 the defcustom, if user\ncustomizations are to be respected.=C2=A0 The simp=
lest way to achieve\nthis is to place the alias statement before the defcus=
tom (this\nis not necessary for aliases that are autoloaded, or in files\nd=
umped with Emacs).=C2=A0 This is so that any user customizations are\nappli=
ed before the defcustom tries to initialize the\nvariable (this is due to t=
he way `defvaralias&#39; works).\n\nFor the benefit of Customize, if OBSOLE=
TE-NAME has\nany of the following properties, they are copied to\nCURRENT-N=
AME, if it does not already have them:\n`saved-value&#39;, `saved-variable-=
comment&#39;.&quot; #&lt;bytecode 0x127e504c6e942a72&gt;)(&#39;sml/time-for=
mat &#39;display-time-format)<br>=C2=A0 macroexpand((define-obsolete-variab=
le-alias &#39;sml/time-format &#39;display-time-format) ((sml/-debug . #f(c=
ompiled-function (fmt &amp;rest r) #&lt;bytecode -0x528c1381ccb3bab&gt;)) (=
declare-function . byte-compile-macroexpand-declare-function) (eval-when-co=
mpile . #f(compiled-function (&amp;rest body) #&lt;bytecode -0xcee878b9e5c4=
79&gt;)) (eval-and-compile . #f(compiled-function (&amp;rest body) #&lt;byt=
ecode 0x31ea4933231cd9b&gt;)) (with-suppressed-warnings . #f(compiled-funct=
ion (warnings &amp;rest body) #&lt;bytecode 0x11867883d853666e&gt;))))<br>=
=C2=A0 macroexp-macroexpand((define-obsolete-variable-alias &#39;sml/time-f=
ormat &#39;display-time-format) ((sml/-debug . #f(compiled-function (fmt &a=
mp;rest r) #&lt;bytecode -0x528c1381ccb3bab&gt;)) (declare-function . byte-=
compile-macroexpand-declare-function) (eval-when-compile . #f(compiled-func=
tion (&amp;rest body) #&lt;bytecode -0xcee878b9e5c479&gt;)) (eval-and-compi=
le . #f(compiled-function (&amp;rest body) #&lt;bytecode 0x31ea4933231cd9b&=
gt;)) (with-suppressed-warnings . #f(compiled-function (warnings &amp;rest =
body) #&lt;bytecode 0x11867883d853666e&gt;))))<br>=C2=A0 byte-compile-recur=
se-toplevel((define-obsolete-variable-alias &#39;sml/time-format &#39;displ=
ay-time-format) #&lt;subr F616e6f6e796d6f75732d6c616d626461_anonymous_lambd=
a_45&gt;)<br>=C2=A0 byte-compile-toplevel-file-form((define-obsolete-variab=
le-alias &#39;sml/time-format &#39;display-time-format))<br>=C2=A0 #&lt;sub=
r F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_43&gt;(#&lt;buffer =C2=
=A0*Compiler Input*&gt;)<br>=C2=A0 byte-compile-from-buffer(#&lt;buffer =C2=
=A0*Compiler Input*&gt;)<br>=C2=A0 byte-compile-file(&quot;c:/Users/xxx/.em=
acs.d/elpa/smart-mode-line-2019...&quot;)<br>=C2=A0 #f(compiled-function (f=
ilename) &quot;Byte-compile FILENAME spilling data from the byte compiler.&=
quot; #&lt;bytecode 0x8fb180dc298647e&gt;)(&quot;c:/Users/xxx/.emacs.d/elpa=
/smart-mode-line-2019...&quot;)<br>=C2=A0 apply(#f(compiled-function (filen=
ame) &quot;Byte-compile FILENAME spilling data from the byte compiler.&quot=
; #&lt;bytecode 0x8fb180dc298647e&gt;) &quot;c:/Users/xxx/.emacs.d/elpa/sma=
rt-mode-line-2019...&quot; nil)<br>=C2=A0 comp-spill-lap-function(&quot;c:/=
Users/xxx/.emacs.d/elpa/smart-mode-line-2019...&quot;)<br>=C2=A0 comp-spill=
-lap(&quot;c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...&quot;)<br>=C2=
=A0 #f(compiled-function (pass) #&lt;bytecode 0x1a1ac110a850427c&gt;)(comp-=
spill-lap)<br>=C2=A0 mapc(#f(compiled-function (pass) #&lt;bytecode 0x1a1ac=
110a850427c&gt;) (comp-spill-lap comp-limplify comp-fwprop comp-call-optim =
comp-ipa-pure comp-add-cstrs comp-fwprop comp-dead-code comp-tco comp-fwpro=
p comp-remove-type-hints comp-final))<br>=C2=A0 comp--native-compile(&quot;=
c:/Users/xxx/.emacs.d/elpa/smart-mode-line-2019...&quot; t)<br>=C2=A0 load-=
with-code-conversion(&quot;c:/Users/xxx/AppData/Local/Temp/emacs-async-com.=
..&quot; &quot;c:/Users/xxx/AppData/Local/Temp/emacs-async-com...&quot; nil=
 t)<br>=C2=A0 command-line-1((&quot;-l&quot; &quot;c:/Users/xxx/AppData/Loc=
al/Temp/emacs-async-com...&quot;))<br>=C2=A0 command-line()<br>=C2=A0 norma=
l-top-level()</div><div>&lt;=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=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=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D&gt;<br></div><br><div><br></div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=
=C2=A0lun. 11 janv. 2021 =C3=A0=C2=A015:48, Andrea Corallo &lt;<a href=3D"m=
ailto:akrl@HIDDEN">akrl@HIDDEN</a>&gt; a =C3=A9crit=C2=A0:<br></div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">=C3=89douard Debry &lt;<a href=
=3D"mailto:edouard.debry@HIDDEN" target=3D"_blank">edouard.debry@HIDDEN=
om</a>&gt; writes:<br>
<br>
&gt; On lun., janv. 11 2021, Andrea Corallo wrote:<br>
&gt;&gt; =C3=89douard Debry &lt;<a href=3D"mailto:edouard.debry@HIDDEN" =
target=3D"_blank">edouard.debry@HIDDEN</a>&gt; writes:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On dim., janv. 10 2021, Andrea Corallo wrote:<br>
&gt;&gt;&gt;&gt; =C3=89douard Debry &lt;<a href=3D"mailto:edouard.debry@gma=
il.com" target=3D"_blank">edouard.debry@HIDDEN</a>&gt; writes:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I noticed that when launching emacs on linux (debian b=
uster),<br>
&gt;&gt;&gt;&gt;&gt; it keeps on running 100% of the CPU and seems to gradu=
ally eat<br>
&gt;&gt;&gt;&gt;&gt; all<br>
&gt;&gt;&gt;&gt;&gt; memory, approximately 1-2% every minute.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; It seems related to native compiling. In the<br>
&gt;&gt;&gt;&gt;&gt; *Async-native-compile-log* I read :<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &lt;=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&gt;<br>
&gt;&gt;&gt;&gt;&gt; Compiling<br>
&gt;&gt;&gt;&gt;&gt; /home/edouard/.emacs.d/elpa/color-theme-sanityinc-sola=
rized-20200805.603/color-theme-sanityinc-solarized.el...<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I see a similar issue with sanityinc-tomorrow.el, the comp=
ilation<br>
&gt;&gt;&gt;&gt; is<br>
&gt;&gt;&gt;&gt; way<br>
&gt;&gt;&gt;&gt; slower than any other one but it completes eventually.=C2=
=A0 I guess is<br>
&gt;&gt;&gt;&gt; the<br>
&gt;&gt;&gt;&gt; same issue you see and with sufficient RAM also<br>
&gt;&gt;&gt;&gt; sanityinc-solarized<br>
&gt;&gt;&gt;&gt; should complete.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In case of of sanityinc-tomorrow I think is because of<br>
&gt;&gt;&gt;&gt; `color-theme-sanityinc-tomorrow&#39;.=C2=A0 This is a sing=
le function that<br>
&gt;&gt;&gt;&gt; after<br>
&gt;&gt;&gt;&gt; macro expansion becomes enormous.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; We need to make the compiler robust against these corner c=
ases,<br>
&gt;&gt;&gt;&gt; I&#39;ll<br>
&gt;&gt;&gt;&gt; have a look this week into adding some logic for that.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;=C2=A0 =C2=A0Andrea<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I have waited for approximately one hour and until linux becam=
e<br>
&gt;&gt;&gt; totally unresponsive, I had to reboot.<br>
&gt;&gt;<br>
&gt;&gt; Right, these are the classical symptoms of a system swapping for<b=
r>
&gt;&gt; insufficient physical memory (or excessive mem usage by a program =
:)<br>
&gt;<br>
&gt; Probably, my previous bug report &quot;Excessive memory ...&quot; was =
due to<br>
&gt; this package<br>
&gt; trying to be natively compiled. I will try the<br>
&gt; &quot;comp-deferred-compilation-deny-list&quot;<br>
&gt; setting on windows 10 so as to be sure there is nothing more.<br>
<br>
Thanks, let us know so in case we can close the duplicate.<br>
<br>
=C2=A0 Andrea<br>
</blockquote></div>

--000000000000b5352d05b8b116af--




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 14:49:01 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 09:49:00 2021
Received: from localhost ([127.0.0.1]:56287 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyyVA-0003tx-LD
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 09:49:00 -0500
Received: from mx.sdf.org ([205.166.94.24]:60097)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kyyV9-0003tp-63
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 09:48:59 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10BEmvPr015598;
 Mon, 11 Jan 2021 14:48:57 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <xjfy2gzg4of.fsf@HIDDEN>
 <87sg77yat7.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 14:48:57 +0000
In-Reply-To: <87sg77yat7.fsf@HIDDEN> (=?utf-8?Q?=22=C3=89douard?=
 Debry"'s message of "Mon, 11 Jan 2021 12:25:56 +0100")
Message-ID: <xjfczybfs12.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

=C3=89douard Debry <edouard.debry@HIDDEN> writes:

> On lun., janv. 11 2021, Andrea Corallo wrote:
>> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>>
>>> On dim., janv. 10 2021, Andrea Corallo wrote:
>>>> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>>>>
>>>>> I noticed that when launching emacs on linux (debian buster),
>>>>> it keeps on running 100% of the CPU and seems to gradually 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 compilation
>>>> is
>>>> way
>>>> slower than any other one but it completes eventually.  I guess is
>>>> the
>>>> same issue you see and with sufficient RAM also
>>>> sanityinc-solarized
>>>> should complete.
>>>>
>>>> In case of of sanityinc-tomorrow I think is because of
>>>> `color-theme-sanityinc-tomorrow'.  This is a single function that
>>>> after
>>>> macro expansion becomes enormous.
>>>>
>>>> We need to make the compiler robust against these corner 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 program :)
>
> Probably, my previous bug report "Excessive memory ..." was due to
> this package
> trying to be natively compiled. I will try the
> "comp-deferred-compilation-deny-list"
> setting on windows 10 so as to be sure there is nothing more.

Thanks, let us know so in case we can close the duplicate.

  Andrea




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 11:26:11 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 06:26:11 2021
Received: from localhost ([127.0.0.1]:55889 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyvKt-0000DB-3Z
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 06:26:11 -0500
Received: from mail-pl1-f175.google.com ([209.85.214.175]:45891)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kyvKr-0000Cv-BB
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 06:26:09 -0500
Received: by mail-pl1-f175.google.com with SMTP id e2so9326692plt.12
 for <45751 <at> 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)
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)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <xjfy2gzg4of.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Andrea Corallo <akrl@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <xjfy2gzg4of.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 12:25:56 +0100
Message-ID: <87sg77yat7.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On lun., janv. 11 2021, Andrea Corallo wrote:
> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>
>> On dim., janv. 10 2021, Andrea Corallo wrote:
>>> =C3=89douard Debry <edouard.debry@HIDDEN> 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





Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 11:24:10 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 06:24:10 2021
Received: from localhost ([127.0.0.1]:55873 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyvIv-0008R1-2O
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 06:24:09 -0500
Received: from mail-pf1-f181.google.com ([209.85.210.181]:42126)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kyvIt-0008QZ-3S
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 06:24:07 -0500
Received: by mail-pf1-f181.google.com with SMTP id h10so10753077pfo.9
 for <45751 <at> 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)
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)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <87h7nojsll.fsf@HIDDEN>
 <xjfturng4m2.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Andrea Corallo <akrl@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <xjfturng4m2.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 12:23:54 +0100
Message-ID: <87turnyawl.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On lun., janv. 11 2021, Andrea Corallo wrote:
> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>
>> On lun., janv. 11 2021, =C3=89douard Debry wrote:
>>> On dim., janv. 10 2021, Andrea Corallo wrote:
>>>> =C3=89douard Debry <edouard.debry@HIDDEN> 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





Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 10:26:03 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 05:26:03 2021
Received: from localhost ([127.0.0.1]:55747 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyuOh-0006q2-Fx
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:26:03 -0500
Received: from mx.sdf.org ([205.166.94.24]:63746)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kyuOf-0006pd-Ej
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:26:01 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10BAPxtb022110;
 Mon, 11 Jan 2021 10:26:00 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <83r1msf93z.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 10:25:59 +0000
In-Reply-To: <83r1msf93z.fsf@HIDDEN> (Eli Zaretskii's message of "Mon, 11 Jan
 2021 05:25:20 +0200")
Message-ID: <xjfpn2bg47c.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: edouard.debry@HIDDEN, 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

Eli Zaretskii <eliz@HIDDEN> writes:

>> Date: Sun, 10 Jan 2021 20:14:53 +0000
>> Cc: 45751 <at> debbugs.gnu.org
>> From: Andrea Corallo via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@HIDDEN>
>> 
>> > 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 compilation is way
>> slower than any other one but it completes eventually.  I guess is the
>> same issue you see and with sufficient RAM also sanityinc-solarized
>> should complete.
>> 
>> In case of of sanityinc-tomorrow I think is because of
>> `color-theme-sanityinc-tomorrow'.  This is a single function that after
>> macro expansion becomes enormous.
>> 
>> We need to make the compiler robust against these corner cases, I'll
>> have a look this week into adding some logic for that.
>
> Maybe we should have a "no-native-compile" cookie for these cases.
> After all, compiling a theme will not really speed up anything
> important, right?

Agreed, that's a good idea.

At the moment similar mechanisms are:

- Declare a function with (declare (speed -1)) will include the
  function in the .eln but in byte-code form.

- Have comp-speed to -1 as file variable in the source file should
  produce an eln containing only byte-code functions.

But yeah, a dedicated cookie is better because there's no point of
producing the .eln file at all for cases like this.

  Andrea




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 10:17:12 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 05:17:11 2021
Received: from localhost ([127.0.0.1]:55722 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyuG7-0006c2-Lm
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:17:11 -0500
Received: from mx.sdf.org ([205.166.94.24]:64924)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kyuG6-0006bu-6U
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:17:10 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10BAH98C024215;
 Mon, 11 Jan 2021 10:17:09 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN> <87h7nojsll.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 10:17:09 +0000
In-Reply-To: <87h7nojsll.fsf@HIDDEN> (=?utf-8?Q?=22=C3=89douard?=
 Debry"'s message of "Mon, 11 Jan 2021 00:10:46 +0100")
Message-ID: <xjfturng4m2.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

=C3=89douard Debry <edouard.debry@HIDDEN> writes:

> On lun., janv. 11 2021, =C3=89douard Debry wrote:
>> On dim., janv. 10 2021, Andrea Corallo wrote:
>>> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>>>
>>>> I noticed that when launching emacs on linux (debian buster),
>>>> it keeps on running 100% of the CPU and seems to gradually 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 compilation
>>> is way
>>> slower than any other one but it completes eventually.  I guess is
>>> the
>>> same issue you see and with sufficient RAM also sanityinc-solarized
>>> should complete.
>>>
>>> In case of of sanityinc-tomorrow I think is because of
>>> `color-theme-sanityinc-tomorrow'.  This is a single function that
>>> after
>>> macro expansion becomes enormous.
>>>
>>> We need to make the compiler robust against these corner 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.
>>
>> I am not 100% sure it is because of emacs compiling the color theme
>> package and eating
>> all memory,
>> but I never had such a crash on linux since I own this laptop 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 try
>> another theme and see
>> if this still happens.
>>
>> Regards
>
> Also, is there a way to prevent emacs native-comp to compile some
> packages, some kind
> of blacklist. I would prefer at the moment because I am used to this
> color theme.

Yes, `comp-deferred-compilation-deny-list'.

> Do you think there may be a noticeable difference on emacs's
> performance between a
> color theme natively compiled (*eln) or just byte compiled (*elc)

I don't think so.

  Andrea




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 10:15:49 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 05:15:49 2021
Received: from localhost ([127.0.0.1]:55710 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyuEn-0006Z9-6Z
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:15:49 -0500
Received: from mx.sdf.org ([205.166.94.24]:65105)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kyuEk-0006Yz-A5
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 05:15:47 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10BAFjWq015860;
 Mon, 11 Jan 2021 10:15:45 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 10:15:44 +0000
In-Reply-To: <87im84jsu0.fsf@HIDDEN> (=?utf-8?Q?=22=C3=89douard?=
 Debry"'s message of "Mon, 11 Jan 2021 00:05:43 +0100")
Message-ID: <xjfy2gzg4of.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

=C3=89douard Debry <edouard.debry@HIDDEN> writes:

> On dim., janv. 10 2021, Andrea Corallo wrote:
>> =C3=89douard Debry <edouard.debry@HIDDEN> writes:
>>
>>> I noticed that when launching emacs on linux (debian buster),
>>> it keeps on running 100% of the CPU and seems to gradually 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.60=
3/color-theme-sanityinc-solarized.el...
>>
>> I see a similar issue with sanityinc-tomorrow.el, the compilation is
>> way
>> slower than any other one but it completes eventually.  I guess is
>> the
>> same issue you see and with sufficient RAM also sanityinc-solarized
>> should complete.
>>
>> In case of of sanityinc-tomorrow I think is because of
>> `color-theme-sanityinc-tomorrow'.  This is a single function that
>> after
>> macro expansion becomes enormous.
>>
>> We need to make the compiler robust against these corner 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 program :)




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 08:10:39 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 03:10:39 2021
Received: from localhost ([127.0.0.1]:55524 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kysHf-0003Lt-8m
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 03:10:39 -0500
Received: from mail-pf1-f177.google.com ([209.85.210.177]:42353)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kysHe-0003Ld-08
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 03:10:38 -0500
Received: by mail-pf1-f177.google.com with SMTP id h10so10475650pfo.9
 for <45751 <at> debbugs.gnu.org>; Mon, 11 Jan 2021 00:10:37 -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=tz0cjgIyZ3/D5ICgkfd4OaSqYsaZOaORL32JHzgTrVo=;
 b=UuK4HpKUmlrtBu0pM7iD/v1FTY+1RfGz4MQoVDbw8NaLGAKstEiziFOtmU44I7YZJJ
 j4WNF1rXNOPT/YSwJJ1Kuu1zR0oVf4eNWseO9oKOzJbAl26xGL+y7NyA9WVlgLznyV3I
 u++rdUxDjFZj0ddVOWt3mprqybLQV5BVH61IQ8G8jM+UJqCL5Hz5qt9lQh4eiCq8AJXX
 JPQUUb/EZpliiyZCs1YYi1xUlE019mOCV2ZI1PSqbGU1JilVMx4vlqSjJlHY5YqEj3L1
 Rgw0XxMbgA5tnhInlSeiEQkcb/GB1wevXKUDsaPLU+WMzBvaYSW7jM335Z+jovRxzDku
 Jodg==
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=tz0cjgIyZ3/D5ICgkfd4OaSqYsaZOaORL32JHzgTrVo=;
 b=AfqBiLLTu91YJHHMvZDHhaD98T7I5wBIlfUSewob8Fb9ODgYUypQotnrR3M+ytRQyc
 xak1NfNlVzKH74fASsBP094AFW91DYY5LfgrNExwfMdRi41Y2KylGXXmBo7NROVXsyuj
 07CGsyb5HXVNC9wfiAvNK2GhBTQvXnISEmAY47j2tig/TK7SjiZqZAjaq93UNlnU6yUz
 xPclBVIR3T0g5ijQ6eS9W++Z0kLhjg2tHYDDwtzz5gt0Mt7jRqmwsp3LEQEcG1l7UTZd
 Y3/E2mnGLXqk8dICEi4YRGlcc/BSu1LnX8BNqVzn9AksDb5Iuzp8kObfDt8kFiJ1/CmK
 vR2A==
X-Gm-Message-State: AOAM531yX/0HUtiPdAxHJJ6uDpEuL4xOXo2vCCsCWF7cphxDuj34S8fN
 /DvikM8ArNtQQD8MWNx41zMgIznSAzTt8Q==
X-Google-Smtp-Source: ABdhPJwiXaE0VPfkMv0kqKEWqSRYNzuCFfOCdRBuLpIw1umK+CTYvHWRfc+5acqyGkoOss21SNJnhw==
X-Received: by 2002:a63:2cd:: with SMTP id 196mr18773229pgc.398.1610352632222; 
 Mon, 11 Jan 2021 00:10:32 -0800 (PST)
Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14])
 by smtp.gmail.com with ESMTPSA id d36sm19330380pgm.77.2021.01.11.00.10.28
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 11 Jan 2021 00:10:31 -0800 (PST)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <83r1msf93z.fsf@HIDDEN> <87turnvr2k.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <87turnvr2k.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 09:10:21 +0100
Message-ID: <87mtxfj3ma.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org, Andrea Corallo <akrl@HIDDEN>
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On lun., janv. 11 2021, =C3=89douard Debry wrote:
> On lun., janv. 11 2021, Eli Zaretskii wrote:
>>> Date: Sun, 10 Jan 2021 20:14:53 +0000
>>> Cc: 45751 <at> debbugs.gnu.org
>>> From: Andrea Corallo via "Bug reports for GNU Emacs,
>>>  the Swiss army knife of text editors" <bug-gnu-emacs@HIDDEN>
>>>  > 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.
>>
>> Maybe we should have a "no-native-compile" cookie for these=20
>> cases.
>> After all, compiling a theme will not really speed up anything
>> important, right?
>
> This is more or less what I advocated with a native compile=20
> blacklist.
>
> At the moment, it would help me if it is possible to toggle=20
> native compilation.
> In my config file there is :
>
> (setq package-native-compile t)
>
> If I set it to nil, does it mean that, on startup, emacs will=20
> not try to natively
> compile
> any packages ?

Answering to my own question, it seems that no. Is there an emacs=20
command to kill the
native compiling process ? It seems that closing the log buffer=20
has this effect, but there
is probably a better way.





Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 08:03:09 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Mon Jan 11 03:03:09 2021
Received: from localhost ([127.0.0.1]:55492 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kysAP-0003A9-5w
	for submit <at> debbugs.gnu.org; Mon, 11 Jan 2021 03:03:09 -0500
Received: from mail-wr1-f41.google.com ([209.85.221.41]:44556)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kysAN-00039r-L8
 for 45751 <at> debbugs.gnu.org; Mon, 11 Jan 2021 03:03:08 -0500
Received: by mail-wr1-f41.google.com with SMTP id w5so15304305wrm.11
 for <45751 <at> debbugs.gnu.org>; Mon, 11 Jan 2021 00:03: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;
 bh=lhjZ2fWkSVpTyjYSuaYNmEHkPhvAAI33IlhOpt61R2k=;
 b=KEJBC2HHRtbkclWZrxvw0ZyzqfIG2FKNMQXEwrLGhMtkxXfOpHNRMQY5LsabaM49b6
 4+mK/oOuXqwEDaTh9xBFBSt/LHkgMuXSdkvqGGOJeF3jEli6YdCHqpWnRGh2E4SPH02N
 h5hfDaqziLSA6h85npPWpSC1WMfd+i/+cdT/IsTLPF6XrGu7Dg0smOQ5XajaEePAOkYk
 lAGLIqpoEgiEsQjEWmkflNrXUtsTb8N2jSnXcy3pWFn75c66lW1Lnv/+IKhHEOSm9K4B
 7PgawXYi/jSKfdxWLL9N/Y/zsGkRPWfwR6Tz7Emk00+u7yRaW6ru9nsXKJhiLSZ/m4Ct
 YCDA==
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;
 bh=lhjZ2fWkSVpTyjYSuaYNmEHkPhvAAI33IlhOpt61R2k=;
 b=I9qfr0ct5NKJhJauvANCxz3OUbntuJdEqEKgzAEF0PVIYqg/WsHzpHBgJEsD8gEy+2
 kl3JEX5XEfZMd4xHJ1JPQWJAF3KEmsUDS2DODFZvubPi+RNeiWhFmgdbG9bSbKJ/cED6
 9OZ8UXiIDB416rjg3AWaesh+6JaswFN9h5h7F128FMyDBASCM7LGzbi/zlfd36DKmONe
 PPIB+GxMDgnyVtOqVwC/sGCOHiyLzxKzKdeGzNnbnfe0c0pGfXuEjl5tLgeZULMTEGhI
 88BIZPMSHNs7Cxz1ArT6jwlIk4qQDtPuqJfTC2w1phmxHNg2i/w6xeocN9hBke0qfNuW
 /zuw==
X-Gm-Message-State: AOAM533y6QrjQe695koVqlVCa68Q3IU2i+KJ4UbwaSsyfFrY5bRg0Rfv
 N8dM7BC09KGTow8EDKmwIjTMnAda9xN8zw==
X-Google-Smtp-Source: ABdhPJyKeQBZTrpRhT156BrqzzeUMrn0ODBnucGPzGS+vrBqkD+VKjZMY3sEFlJFLdimeIlAVYgKXQ==
X-Received: by 2002:a5d:67c1:: with SMTP id n1mr14903119wrw.205.1610352181700; 
 Mon, 11 Jan 2021 00:03:01 -0800 (PST)
Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14])
 by smtp.gmail.com with ESMTPSA id u66sm21389880wmg.30.2021.01.11.00.03.00
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Mon, 11 Jan 2021 00:03:01 -0800 (PST)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <83r1msf93z.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Eli Zaretskii <eliz@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <83r1msf93z.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 09:02:59 +0100
Message-ID: <87turnvr2k.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Spam-Score: 0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org, Andrea Corallo <akrl@HIDDEN>
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On lun., janv. 11 2021, Eli Zaretskii wrote:
>> Date: Sun, 10 Jan 2021 20:14:53 +0000
>> Cc: 45751 <at> debbugs.gnu.org
>> From: Andrea Corallo via "Bug reports for GNU Emacs,
>>  the Swiss army knife of text editors" <bug-gnu-emacs@HIDDEN>
>> 
>> > 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 
>> compilation is way
>> slower than any other one but it completes eventually.  I guess 
>> is the
>> same issue you see and with sufficient RAM also 
>> sanityinc-solarized
>> should complete.
>> 
>> In case of of sanityinc-tomorrow I think is because of
>> `color-theme-sanityinc-tomorrow'.  This is a single function 
>> that after
>> macro expansion becomes enormous.
>> 
>> We need to make the compiler robust against these corner cases, 
>> I'll
>> have a look this week into adding some logic for that.
>
> Maybe we should have a "no-native-compile" cookie for these 
> cases.
> After all, compiling a theme will not really speed up anything
> important, right?

This is more or less what I advocated with a native compile 
blacklist.

At the moment, it would help me if it is possible to toggle native 
compilation.
In my config file there is :

(setq package-native-compile t)

If I set it to nil, does it mean that, on startup, emacs will not 
try to natively compile
any packages ?

Regards




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 11 Jan 2021 03:25:41 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Jan 10 22:25:41 2021
Received: from localhost ([127.0.0.1]:55328 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kynpt-0004L3-Hi
	for submit <at> debbugs.gnu.org; Sun, 10 Jan 2021 22:25:41 -0500
Received: from eggs.gnu.org ([209.51.188.92]:54854)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <eliz@HIDDEN>) id 1kynps-0004Kp-3Y
 for 45751 <at> debbugs.gnu.org; Sun, 10 Jan 2021 22:25:40 -0500
Received: from fencepost.gnu.org ([2001:470:142:3::e]:57852)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@HIDDEN>)
 id 1kynpk-0001cw-GY; Sun, 10 Jan 2021 22:25:32 -0500
Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1645
 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@HIDDEN>)
 id 1kynpP-0008RV-5E; Sun, 10 Jan 2021 22:25:26 -0500
Date: Mon, 11 Jan 2021 05:25:20 +0200
Message-Id: <83r1msf93z.fsf@HIDDEN>
From: Eli Zaretskii <eliz@HIDDEN>
To: Andrea Corallo <akrl@HIDDEN>
In-Reply-To: <xjfft38a6rm.fsf@HIDDEN> (bug-gnu-emacs@HIDDEN)
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
X-Spam-Score: -2.3 (--)
X-Debbugs-Envelope-To: 45751
Cc: edouard.debry@HIDDEN, 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -3.3 (---)

> Date: Sun, 10 Jan 2021 20:14:53 +0000
> Cc: 45751 <at> debbugs.gnu.org
> From: Andrea Corallo via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@HIDDEN>
> 
> > 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 compilation is way
> slower than any other one but it completes eventually.  I guess is the
> same issue you see and with sufficient RAM also sanityinc-solarized
> should complete.
> 
> In case of of sanityinc-tomorrow I think is because of
> `color-theme-sanityinc-tomorrow'.  This is a single function that after
> macro expansion becomes enormous.
> 
> We need to make the compiler robust against these corner cases, I'll
> have a look this week into adding some logic for that.

Maybe we should have a "no-native-compile" cookie for these cases.
After all, compiling a theme will not really speed up anything
important, right?




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 10 Jan 2021 23:11:01 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Jan 10 18:11:01 2021
Received: from localhost ([127.0.0.1]:55124 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyjrR-0003r4-0O
	for submit <at> debbugs.gnu.org; Sun, 10 Jan 2021 18:11:01 -0500
Received: from mail-pf1-f174.google.com ([209.85.210.174]:36991)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kyjrP-0003qc-F3
 for 45751 <at> debbugs.gnu.org; Sun, 10 Jan 2021 18:10:59 -0500
Received: by mail-pf1-f174.google.com with SMTP id 11so9881153pfu.4
 for <45751 <at> 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)
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)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
 <87im84jsu0.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Andrea Corallo <akrl@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <87im84jsu0.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 00:10:46 +0100
Message-ID: <87h7nojsll.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On lun., janv. 11 2021, =C3=89douard Debry wrote:
> On dim., janv. 10 2021, Andrea Corallo wrote:
>> =C3=89douard Debry <edouard.debry@HIDDEN> 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




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 10 Jan 2021 23:06:00 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Jan 10 18:06:00 2021
Received: from localhost ([127.0.0.1]:55112 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyjmZ-0003VP-RN
	for submit <at> debbugs.gnu.org; Sun, 10 Jan 2021 18:06:00 -0500
Received: from mail-pj1-f41.google.com ([209.85.216.41]:55607)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kyjmX-0003Uu-7k
 for 45751 <at> debbugs.gnu.org; Sun, 10 Jan 2021 18:05:58 -0500
Received: by mail-pj1-f41.google.com with SMTP id p12so6660991pju.5
 for <45751 <at> debbugs.gnu.org>; Sun, 10 Jan 2021 15:05:57 -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=KYRqH798VumwEzzF4EYVCn6muari7hluJEkAbGqZl9A=;
 b=NF+iDc8bTAcTfAVU16cutxbpapVwfB2LWMw3LxizuwS2zkLjivtMZZvykJtqXWpbYC
 +NzVR7orqY6Tyf3bIK+I05zN9JFxotx6iRWi0DIS+N1lEY7hKqPdcX1YzwdRVt2mAOq7
 BDVuwxvyqGAtqXVH5dYUkW3sc7UI5Ym5ewf03nj4txDMo91JixGLBAEP7VtNRf/7T6mg
 CWfUUj5hr7fwAgiDVrXKNA9rXjLMJL/9ysTaszaz7fynWcXKxCuyPCuii3/SCPKF7Kf8
 iRxarwKroyChrUI0sFt484/y5MHNjBiG74nxKZ5i+F2jm8dThJmoASZU81DiRu0yUepW
 6DYQ==
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=KYRqH798VumwEzzF4EYVCn6muari7hluJEkAbGqZl9A=;
 b=WKSfgNSPTZ5JoYlvT5Z62c3hF4xUNbU3JYfDAxixftkY4kJRDiIcH8nUD2q8LmYMc3
 B0I5nrejnoQj84yXX40qFGrhTdiAc2BB4zbP3z2TWeyVs/m59whC6HWv/1YwjSjyG08P
 VGK1dJ2LDGs8UVm2EPzy930W+oZycJQObAN4ee1Px9UgEfea1HhT7q0uWd3d96Q21VdO
 CaIr2/CFvuy9SFCd8nciuorbJio7XZvefwnkAPfPXw75W3EhuWrqILkIorSRgzlys71t
 xsaBo74ST42W4qONPHV0OpOemg/bghMNwK9huTwDMKNGlFEQrLeY+DPWGQdlGovfdkem
 4Mkw==
X-Gm-Message-State: AOAM531jG319wffJ25mtdIE6IrC+b+rULBnUgjWiK7nABex3Un0IlH99
 LngceC4HgzwNZ3ZeQ6FFM3v4Tdb6cE0=
X-Google-Smtp-Source: ABdhPJzk9BHyqRn5QKDn9+UMMytynn+gnhF8X5yzpVvcYukviSE40OBzrcy+9ZlFEdX1vsMnGoc6gQ==
X-Received: by 2002:a17:90a:8985:: with SMTP id
 v5mr14458192pjn.27.1610319951339; 
 Sun, 10 Jan 2021 15:05:51 -0800 (PST)
Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14])
 by smtp.gmail.com with ESMTPSA id k125sm17853736pga.57.2021.01.10.15.05.47
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Sun, 10 Jan 2021 15:05:50 -0800 (PST)
References: <87k0slu13n.fsf@HIDDEN> <xjfft38a6rm.fsf@HIDDEN>
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: Andrea Corallo <akrl@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
In-reply-to: <xjfft38a6rm.fsf@HIDDEN>
Date: Mon, 11 Jan 2021 00:05:43 +0100
Message-ID: <87im84jsu0.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)


On dim., janv. 10 2021, Andrea Corallo wrote:
> =C3=89douard Debry <edouard.debry@HIDDEN> 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.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 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 and=20
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 try=20
another theme and see if this still happens.

Regards




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at 45751 <at> debbugs.gnu.org:


Received: (at 45751) by debbugs.gnu.org; 10 Jan 2021 20:15:00 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Jan 10 15:14:59 2021
Received: from localhost ([127.0.0.1]:55014 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyh75-0005hf-J7
	for submit <at> debbugs.gnu.org; Sun, 10 Jan 2021 15:14:59 -0500
Received: from mx.sdf.org ([205.166.94.24]:59371)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <akrl@HIDDEN>) id 1kyh72-0005hJ-JS
 for 45751 <at> debbugs.gnu.org; Sun, 10 Jan 2021 15:14:58 -0500
Received: from mab (ma.sdf.org [205.166.94.33])
 by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 10AKErtP008905;
 Sun, 10 Jan 2021 20:14:54 GMT
From: Andrea Corallo <akrl@HIDDEN>
To: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
Subject: Re: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
References: <87k0slu13n.fsf@HIDDEN>
Date: Sun, 10 Jan 2021 20:14:53 +0000
In-Reply-To: <87k0slu13n.fsf@HIDDEN> (=?utf-8?Q?=22=C3=89douard?=
 Debry"'s message of "Sun, 10 Jan 2021 00:44:44 +0100")
Message-ID: <xjfft38a6rm.fsf@HIDDEN>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -0.0 (/)
X-Debbugs-Envelope-To: 45751
Cc: 45751 <at> debbugs.gnu.org
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -1.0 (-)

=C3=89douard Debry <edouard.debry@HIDDEN> writes:

> I noticed that when launching emacs on linux (debian buster),
> it keeps on running 100% of the CPU and seems to gradually 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 compilation is way
slower than any other one but it completes eventually.  I guess is the
same issue you see and with sufficient RAM also sanityinc-solarized
should complete.

In case of of sanityinc-tomorrow I think is because of
`color-theme-sanityinc-tomorrow'.  This is a single function that after
macro expansion becomes enormous.

We need to make the compiler robust against these corner cases, I'll
have a look this week into adding some logic for that.

Thanks

  Andrea




Information forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.

Message received at submit <at> debbugs.gnu.org:


Received: (at submit) by debbugs.gnu.org; 9 Jan 2021 23:45:00 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sat Jan 09 18:45:00 2021
Received: from localhost ([127.0.0.1]:52755 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1kyNum-0003ph-Ba
	for submit <at> debbugs.gnu.org; Sat, 09 Jan 2021 18:45:00 -0500
Received: from lists.gnu.org ([209.51.188.17]:41580)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <edouard.debry@HIDDEN>) id 1kyNuk-0003pZ-Ec
 for submit <at> debbugs.gnu.org; Sat, 09 Jan 2021 18:44:59 -0500
Received: from eggs.gnu.org ([2001:470:142:3::10]:42290)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <edouard.debry@HIDDEN>)
 id 1kyNui-0007p8-EY
 for bug-gnu-emacs@HIDDEN; Sat, 09 Jan 2021 18:44:58 -0500
Received: from mail-wr1-x429.google.com ([2a00:1450:4864:20::429]:45419)
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128)
 (Exim 4.90_1) (envelope-from <edouard.debry@HIDDEN>)
 id 1kyNug-0007JY-Bp
 for bug-gnu-emacs@HIDDEN; Sat, 09 Jan 2021 18:44:56 -0500
Received: by mail-wr1-x429.google.com with SMTP id d26so12492322wrb.12
 for <bug-gnu-emacs@HIDDEN>; Sat, 09 Jan 2021 15:44:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=user-agent:from:to:subject:date:message-id:mime-version
 :content-transfer-encoding;
 bh=28Z9j6oKSmiN1+Et4TUE9J4Bc35aWFAhMfwC9wIUEE0=;
 b=FPWZBfhDS+EQ8ENTj55+lMS3NXnkwrbTQVIGws6BQt6ds35INExeKHIREcIVxyup69
 iOODt/N7xyN9GVtMXzRJYoAbcceGg7qTTQyAPvn4/ddzLeX7kuVv6SBk8++gqRzUCJWS
 9rsMRVUO1bWnTYFAyM5V9Yk+dMb9tIpmaPEAIw9Ofu50mtKtiZZLvqOWsxFhg5Npkewy
 2JnzJjUxIPeYUmV4vIcS7ACNKZKb4HZyIPAUYDD31lGxm6yDvvJDslD4IoRfruU7q2Op
 1MgsNWsiOxV3ref5KzQ4X27YLk1luyTEAuvPErheozSBTO1iTIVkVPID5JJdheO1pNTr
 ZmqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:user-agent:from:to:subject:date:message-id
 :mime-version:content-transfer-encoding;
 bh=28Z9j6oKSmiN1+Et4TUE9J4Bc35aWFAhMfwC9wIUEE0=;
 b=CAn94FWwlr8w5J6ojyM//rn1uBFUZuD8cxJKzXYdII3qav0dPHP3///IyTzIaFNmkc
 pe5tFJh4fYQD9znN4WVRoz/UVlB8e4w2SZN2PsfpH82o465uNVmSP9ouaLEi9bEtWU+f
 vRvgBw/cNcigQLhSPep4nZNMzz8pYI3Z2wLZOc3v0y3N3Ze/8tbiajJP0rigXKP3Tk/r
 s5RnWSldWq+zqXXb9y3cCYW9YzUUJv5se/K2zy+odcHnHJdXp94A6fmUWKPu1g4VLfea
 2YjCa7Mi0jkg7z/JDNYTRyqBhnlZlZMxawo9WDtbxONalFA1P0Jhy2OybTdb498NNMMx
 kIfQ==
X-Gm-Message-State: AOAM531foDRzMpswVV7K4de33yNAE1RJBdtQPlgrdvj9obUhAkCRv95H
 WlyrvM7sCdzn+2ejU/WCEYqY58VnLuo=
X-Google-Smtp-Source: ABdhPJwWgsiisG4ekPIyF/y9rggl8elqH3DmFIDH1L2fzURb+7hu8qF4Oj+IRIplH+xIitBK31kNxQ==
X-Received: by 2002:a5d:5049:: with SMTP id h9mr10250102wrt.404.1610235890500; 
 Sat, 09 Jan 2021 15:44:50 -0800 (PST)
Received: from paquerette (176-142-29-14.abo.bbox.fr. [176.142.29.14])
 by smtp.gmail.com with ESMTPSA id y13sm20342948wrl.63.2021.01.09.15.44.49
 for <bug-gnu-emacs@HIDDEN>
 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
 Sat, 09 Jan 2021 15:44:50 -0800 (PST)
User-agent: mu4e 1.0; emacs 28.0.50
From: =?utf-8?Q?=C3=89douard?= Debry <edouard.debry@HIDDEN>
To: bug-gnu-emacs@HIDDEN
Subject: [feature/native-comp] emacs keeps running 100% of CPU
Date: Sun, 10 Jan 2021 00:44:44 +0100
Message-ID: <87k0slu13n.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=2a00:1450:4864:20::429;
 envelope-from=edouard.debry@HIDDEN; helo=mail-wr1-x429.google.com
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-Debbugs-Envelope-To: submit
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)


I noticed that when launching emacs on linux (debian buster),
it keeps on running 100% of the CPU and seems to gradually eat all
memory, approximately 1-2% every minute.

It seems related to native compiling. In the=20
*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=20
/home/edouard/.emacs.d/elpa/color-theme-sanityinc-solarized-20200805.603/co=
lor-theme-sanityinc-solarized.el...

In color-theme-sanityinc-solarized:
color-theme-sanityinc-solarized.el:850:14: Warning: assignment to=20
free
    variable =E2=80=98ansi-color-names-vector=E2=80=99
color-theme-sanityinc-solarized.el:851:14: Warning: assignment to=20
free
    variable =E2=80=98ansi-color-faces-vector=E2=80=99

In end of data:
color-theme-sanityinc-solarized.el:878:1: Warning: the function
    =E2=80=98color-theme-install=E2=80=99 is not known to be defined.
<=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>

Furthermore "ps x" gives :
 1395 pts/1    Rsl+   7:51 /usr/local/bin/emacs --batch -l=20
 /tmp/emacs-async-comp-color-theme-sanityinc-solarized-ENplTN.el

If I kill this process or close the *Async-native-compile-log,=20
then this disappears.

I do not understand what is the trouble with this package. The=20
native compilation of
this package seems to be endless.

But this could be related to the previous bug "excessive memory=20
..." as I use the
same package theme on windows 10.




Acknowledgement sent to Édouard Debry <edouard.debry@HIDDEN>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs@HIDDEN. Full text available.
Report forwarded to bug-gnu-emacs@HIDDEN:
bug#45751; Package emacs. Full text available.
Please note: This is a static page, with minimal formatting, updated once a day.
Click here to see this page with the latest information and nicer formatting.
Last modified: Tue, 12 Jan 2021 11:15:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.