From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Observing lags or never ending processes
Date: Sun, 11 Sep 2022 15:36:02 +0300 [thread overview]
Message-ID: <Yx3WMo/+BIkl0m1l@protected.localdomain> (raw)
In-Reply-To: <83bkrm9ype.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2022-09-11 10:10]:
> What do you mean by "never ending processes or lags"? Please describe
> in more detail what you do and what you see. Also what version of
> Emacs is that.
Version is GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo version 1.17.6, Xaw3d scroll bars)
of 2022-09-06, Repository revision:
eaca6378d2c4b94bc70a7979642502a80bfacd11
And I observe that since months.
Basically on invokation of a command, something starts happening in
background, preventing command to run straight, and I know that it
would kind of finish execution and my command would run, but it takes
long time. Almost always I interrupt it with C-g multiple times, then
I try again.
It can also happen during writing or normal operations. I am watching
CPU load, so I see CPU load increasing.
Just before minutes, I was doing M-% replacement and then it finds one
term, I answer with `y' and then it finds another one, and so on, then
in middle of that all findings, then something starts in background,
preventing me to do the work.
My timers:
-1d 23h 59m 51.6s 1m battery-update-handler
-1d 23h 59m 51.9s 5.0s proced-auto-update-timer
-1d 23h 59m 59.1s - undo-auto--boundary-timer
26.9s 1m display-time-event-handler
2m 51.6s 5m persistent-scratch-save
2m 53.7s 5m savehist-autosave
2m 54.0s 1h url-cookie-write-file
* 0.1s t show-paren-function
* 0.5s :repeat blink-cursor-start
* 0.5s t #f(compiled-function () #<bytecode 0x12c5e160b85c7bfa> [jit-lock--antiblink-grace-timer jit-lock-context-fontify])
* 1.0s t pabbrev-short-idle-timer
* 1.0s t which-key--update
* 5.0s t pabbrev-idle-timer-function
I see that pabbrev timers are there even if global-pabbrev-mode is
off, maybe turning off that mode should remove timers as well.
Maybe it is some of them. I will try turning them off one by one
during longer periods to observe and maybe find that out.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-09-11 12:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 6:59 Observing lags or never ending processes Jean Louis
2022-09-11 7:06 ` Eli Zaretskii
2022-09-11 12:36 ` Jean Louis [this message]
2022-09-11 13:16 ` Eli Zaretskii
2022-09-11 13:31 ` Jean Louis
2022-09-11 20:21 ` Jean Louis
2022-09-12 2:26 ` Eli Zaretskii
2022-09-12 5:53 ` Jean Louis
2022-09-12 11:19 ` Eli Zaretskii
2022-09-12 12:35 ` Jean Louis
2022-09-12 7:50 ` Jean Louis
2022-09-12 11:32 ` Eli Zaretskii
2022-09-16 19:06 ` Jean Louis
2022-09-17 6:00 ` Eli Zaretskii
2022-09-19 18:43 ` Jean Louis
2022-09-19 19:01 ` Eli Zaretskii
2022-09-20 4:42 ` Jean Louis
2022-09-20 7:54 ` Emanuel Berg
2022-09-22 20:30 ` Jean Louis
2022-09-23 5:30 ` Jean Louis
2022-09-23 6:13 ` Eli Zaretskii
2022-09-23 8:17 ` Jean Louis
2022-09-23 10:42 ` Eli Zaretskii
2022-09-23 14:16 ` Jean Louis
2022-09-24 15:30 ` Emanuel Berg
2022-09-23 11:30 ` Emanuel Berg
2022-09-20 11:20 ` Eli Zaretskii
2022-09-20 18:17 ` Emanuel Berg
2022-09-19 23:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-09-11 15:57 ` Jean Louis
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=Yx3WMo/+BIkl0m1l@protected.localdomain \
--to=bugs@gnu.support \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).