From: "Édouard Debry" <edouard.debry@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 45751@debbugs.gnu.org
Subject: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
Date: Mon, 11 Jan 2021 12:25:56 +0100 [thread overview]
Message-ID: <87sg77yat7.fsf@gmail.com> (raw)
In-Reply-To: <xjfy2gzg4of.fsf@sdf.org>
On lun., janv. 11 2021, Andrea Corallo wrote:
> Édouard Debry <edouard.debry@gmail.com> writes:
>
>> 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.
>
> 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.
Regards
next prev parent reply other threads:[~2021-01-11 11:25 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg77yat7.fsf@gmail.com \
--to=edouard.debry@gmail.com \
--cc=45751@debbugs.gnu.org \
--cc=akrl@sdf.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.