From: Dmitry Antipov <dmantipov@yandex.ru>
To: Lars Andersen <expez@expez.com>
Cc: 16420@debbugs.gnu.org
Subject: bug#16420: 24.3; Drawing an overlay causes 100% cpu utilization
Date: Sun, 12 Jan 2014 20:04:22 +0400 [thread overview]
Message-ID: <52D2BD06.7010905@yandex.ru> (raw)
In-Reply-To: <CACMT31OrOEfzLbfPQnssmQ=suWqA36O05T3dy=wE06KmCtBSPQ@mail.gmail.com>
On 01/12/2014 02:01 AM, Lars Andersen wrote:
> Starting from emacs -Q:
>
> (defface flycheck-warning
> '((((supports :underline (:style wave)))
> :underline (:style wave :color "DarkOrange"))
> (t
> :underline t :inherit warning))
> "Flycheck face for warnings."
> :package-version '(flycheck . "0.13")
> :group 'flycheck-faces)
> (let ((ov (make-overlay (point) (point-at-eol)))
> (face 'flycheck-warning))
> (overlay-put ov 'face face)) ;; C-x C-e this last form to reproduce
Note that C-x C-e has no visible effect until you evaluate first
'defface' form too.
IIUC Emacs itself is still responsible after C-x C-e; could you
please eval (overlays-in (point-min) (point-max)) immediately after?
> After evaluating this elisp, top reports 100% CPU utilization from X.
What about Emacs CPU utilization, and RSS of X and Emacs as well?
Dmitry
next prev parent reply other threads:[~2014-01-12 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 22:01 bug#16420: 24.3; Drawing an overlay causes 100% cpu utilization Lars Andersen
2014-01-12 16:04 ` Dmitry Antipov [this message]
2014-01-12 16:30 ` Eli Zaretskii
2014-01-12 17:53 ` Jan Djärv
2014-01-12 18:00 ` Eli Zaretskii
2014-01-12 18:03 ` Michael Heerdegen
2014-01-13 5:45 ` Dmitry Antipov
2014-01-13 9:35 ` Lars Andersen
2014-01-13 10:04 ` Dmitry Antipov
2014-01-13 10:56 ` Lars Andersen
2014-01-12 17:26 ` bug#16420: Lars Andersen
2014-01-12 18:08 ` bug#16420: Jan Djärv
2014-01-12 18:27 ` bug#16420: Lars Andersen
2014-01-12 18:32 ` bug#16420: Eli Zaretskii
2014-01-12 18:49 ` bug#16420: Jan Djärv
2016-08-09 1:40 ` bug#16420: npostavs
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=52D2BD06.7010905@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=16420@debbugs.gnu.org \
--cc=expez@expez.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).