From: "Édouard Debry" <edouard.debry@gmail.com>
To: 45751@debbugs.gnu.org
Subject: bug#45751: [feature/native-comp] emacs keeps running 100% of CPU
Date: Sun, 10 Jan 2021 00:44:44 +0100 [thread overview]
Message-ID: <87k0slu13n.fsf@gmail.com> (raw)
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...
In color-theme-sanityinc-solarized:
color-theme-sanityinc-solarized.el:850:14: Warning: assignment to
free
variable ‘ansi-color-names-vector’
color-theme-sanityinc-solarized.el:851:14: Warning: assignment to
free
variable ‘ansi-color-faces-vector’
In end of data:
color-theme-sanityinc-solarized.el:878:1: Warning: the function
‘color-theme-install’ is not known to be defined.
<============================>
Furthermore "ps x" gives :
1395 pts/1 Rsl+ 7:51 /usr/local/bin/emacs --batch -l
/tmp/emacs-async-comp-color-theme-sanityinc-solarized-ENplTN.el
If I kill this process or close the *Async-native-compile-log,
then this disappears.
I do not understand what is the trouble with this package. The
native compilation of
this package seems to be endless.
But this could be related to the previous bug "excessive memory
..." as I use the
same package theme on windows 10.
next reply other threads:[~2021-01-09 23:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 23:44 Édouard Debry [this message]
2021-01-10 20:14 ` bug#45751: [feature/native-comp] emacs keeps running 100% of CPU 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
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=87k0slu13n.fsf@gmail.com \
--to=edouard.debry@gmail.com \
--cc=45751@debbugs.gnu.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 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).