all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Slow redisplay
Date: Sun, 25 Aug 2019 14:10:09 +0300	[thread overview]
Message-ID: <83k1b1h566.fsf@gnu.org> (raw)
In-Reply-To: <20190825103251.osstrlohmzp6bmvr@Ergus> (message from Ergus on Sun, 25 Aug 2019 12:32:51 +0200)

> Date: Sun, 25 Aug 2019 12:32:51 +0200
> From: Ergus <spacibba@aol.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
> 
> With the actual master branch I am observing a very important lagging in
> redisplay after being using emacs for 3-4 of hours. The rediplay happens
> like in stop motion speed, I can see the redisplay line being updated
> slowly and it takes sometimes like 1 seconds (from the top to the bottom
> of the screen) in my best laptop.
> 
> (I only use emacs in tui) So the only solution after a while is to close
> emacs and reopen again.
> 
> I used to have these lines:
> 
> (defun my/minibuffer-setup-hook ()
>   (setq gc-cons-threshold most-positive-fixnum))
> 
> (defun my/minibuffer-exit-hook ()
>   (setq gc-cons-threshold 800000))
> 
> (add-hook 'minibuffer-setup-hook #'my/minibuffer-setup-hook)
> (add-hook 'minibuffer-exit-hook #'my/minibuffer-exit-hook)
> 
> In my config, but after removing them (because someone suggested that
> the redisplay lagging could be related with the gc) the problem is still
> there (less critical, but still there after some hours).
> 
> Any suggestion to find where is the issue comming from? Or what should I
> see to make a better report?

If you set garbage-collection-messages non-nil, do you see any GC
messages when Emacs is lagging input?  If so, does invoking "M-x
garbage-collect RET" manual fix that?



  reply	other threads:[~2019-08-25 11:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-25 10:32 Slow redisplay Ergus via Users list for the GNU Emacs text editor
2019-08-25 11:10 ` Eli Zaretskii [this message]
2019-08-26  4:20   ` Ergus
2019-08-26  7:42     ` Eli Zaretskii

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=83k1b1h566.fsf@gnu.org \
    --to=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.
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.