unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Édouard Debry" <edouard.debry@gmail.com>
Cc: 45751@debbugs.gnu.org
Subject: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
Date: Mon, 11 Jan 2021 10:17:09 +0000	[thread overview]
Message-ID: <xjfturng4m2.fsf@sdf.org> (raw)
In-Reply-To: <87h7nojsll.fsf@gmail.com> ("Édouard Debry"'s message of "Mon, 11 Jan 2021 00:10:46 +0100")

Édouard Debry <edouard.debry@gmail.com> writes:

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





  reply	other threads:[~2021-01-11 10:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 23:44 bug#45751: [feature/native-comp] emacs keeps running 100% of CPU Édouard Debry
2021-01-10 20:14 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-10 23:05   ` Édouard Debry
2021-01-10 23:10     ` Édouard Debry
2021-01-11 10:17       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-11 11:23         ` Édouard Debry
2021-01-11 10:15     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-11 11:25       ` Édouard Debry
2021-01-11 14:48         ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-12 10:00           ` edouard debry
2021-01-12 10:56             ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-11  3:25   ` Eli Zaretskii
2021-01-11  8:02     ` Édouard Debry
2021-01-11  8:10       ` Édouard Debry
2021-01-11 10:25     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-19 21:04 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28  8:01   ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xjfturng4m2.fsf@sdf.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=45751@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=edouard.debry@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).