From: Nick H <nick@tenpoint.co.nz>
To: stefan@marxist.se
Cc: "Damien Cassou" <damien@cassou.me>,
"Clément Pit-Claudel" <cpitclaudel@gmail.com>,
26525@debbugs.gnu.org
Subject: bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU
Date: Thu, 03 Sep 2020 11:15:50 +1200 [thread overview]
Message-ID: <6ec4bdf403e191db33a49809e6018025f5624bcf.camel@tenpoint.co.nz> (raw)
In-Reply-To: CADwFkmnHMYW1yVUHUpxJ1mkkW4kP31ocXq+nsqkCw=-Mf7y-jw@mail.gmail.com
> I'm marking this bug as unreproducible for now. Please report back
> if you see this again or can provide any more information.
I just bumped into this bug on 27.1 with the same symptoms - typing lag
after activating flyspell-mode.
I took a couple of profiles - the first when lag was apparent and
another after clearing the lag by toggling flyspell-mode.
Both profiles show a similar result, so the "high cpu" in sit-for might
be a red-herring.
Profile 1 - with lag
- flyspell-post-command-hook 1146 92%
- flyspell-check-word-p 1120 90%
- sit-for 1117 90%
- redisplay 551 44%
+ redisplay_internal (C function) 1 0%
read-event 390 31%
- flyspell-get-not-casechars 1 0%
ispell-get-decoded-string 1 0%
+ flyspell-word 8 0%
+ flyspell-check-pre-word-p 3 0%
+ command-execute 65 5%
+ ... 22 1%
+ undo-auto--add-boundary 1 0%
Profile 2 - without lag
- flyspell-post-command-hook 3507 94%
- flyspell-check-word-p 3432 92%
- sit-for 3414 92%
- redisplay 1660 44%
+ redisplay_internal (C function) 3 0%
+ read-event 1317 35%
+ ispell-get-otherchars 6 0%
+ flyspell-get-not-casechars 5 0%
+ flyspell-word 17 0%
+ flyspell-check-pre-word-p 13 0%
+ command-execute 93 2%
+ ... 87 2%
+ timer-event-handler 3 0%
undo-auto--add-boundary 2 0%
tooltip-hide 1 0%
Nick
next prev parent reply other threads:[~2020-09-02 23:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 20:28 bug#26525: `sit-for' in Flyspell slows typing down, hogs 90% of CPU Clément Pit-Claudel
2017-04-15 20:33 ` Clément Pit-Claudel
2017-04-17 7:14 ` Eli Zaretskii
2017-04-17 13:29 ` Clément Pit-Claudel
2017-04-17 14:25 ` Eli Zaretskii
2017-04-17 15:36 ` Clément Pit-Claudel
2020-08-13 1:41 ` Stefan Kangas
2017-10-17 12:07 ` Damien Cassou
2020-08-28 11:49 ` Stefan Kangas
2020-08-28 12:35 ` Damien Cassou
2020-08-28 18:40 ` Clément Pit-Claudel
2020-08-29 16:27 ` Stefan Kangas
2020-08-29 18:10 ` Clément Pit-Claudel
2020-09-02 23:15 ` Nick H [this message]
2020-09-03 10:19 ` Stefan Kangas
2020-09-04 1:01 ` Nick Helm
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=6ec4bdf403e191db33a49809e6018025f5624bcf.camel@tenpoint.co.nz \
--to=nick@tenpoint.co.nz \
--cc=26525@debbugs.gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=damien@cassou.me \
--cc=stefan@marxist.se \
/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.