From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs memory management and sluggishness
Date: Sun, 28 Jul 2019 05:38:25 +0300 [thread overview]
Message-ID: <83imrmlw7y.fsf@gnu.org> (raw)
In-Reply-To: <8736ir3uj0.fsf@telefonica.net> (message from Óscar Fuentes on Sun, 28 Jul 2019 01:52:19 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: emacs-devel@gnu.org
> Date: Sun, 28 Jul 2019 01:52:19 +0200
>
> It occurred to me to take a look at M-x list-timers and it showed about
> 700 (seven hundred) of them. The most frequent was about 300 repetitions
> of
>
> * 0.05 t aggressive-indent--indent-if-changed
>
> which is created by aggressive-indent-mode, that I use on a subset of my
> buffers, then several dozens of
>
> * 0.50 t pdf-cache--prefetch-start
>
> which comes from pdf-tools, and dozens of
>
> 6467.37 - password-cache-remove
>
> (the Next number varies, of course). So I used cancel-function-timers to
> get rid of all the instances of those 3 examples and the lag while
> typing text went away.
Yes, excess number of timers can produce lags.
> Now I'll do what you advised: fresh build, fresh instance and watch for
> memory (and timers) increase.
Suggest to start a bug report and accumulate all the data there.
next prev parent reply other threads:[~2019-07-28 2:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 19:20 Emacs memory management and sluggishness Óscar Fuentes
2019-07-27 6:55 ` Eli Zaretskii
2019-07-27 12:36 ` Óscar Fuentes
2019-07-27 13:20 ` Eli Zaretskii
2019-07-27 23:52 ` Óscar Fuentes
2019-07-28 2:38 ` Eli Zaretskii [this message]
2019-07-31 20:54 ` Joseph Mingrone
2019-07-31 22:00 ` Óscar Fuentes
2019-07-31 22:14 ` Joseph Mingrone
2019-07-31 22:19 ` Óscar Fuentes
2019-07-31 22:27 ` Joseph Mingrone
2019-08-01 2:43 ` Eli Zaretskii
2019-08-01 9:46 ` Joseph Mingrone
2019-08-01 13:49 ` Eli Zaretskii
2019-08-10 2:28 ` Joseph Mingrone
2019-08-10 7:43 ` Eli Zaretskii
2019-08-11 20:30 ` Joseph Mingrone
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=83imrmlw7y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.