all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@newcastle.ac.uk
Cc: 20134@debbugs.gnu.org
Subject: bug#20134: Acknowledgement (24.4.90; Emacs slowdown to eventual hang)
Date: Tue, 07 Apr 2015 17:56:46 +0300	[thread overview]
Message-ID: <83iod8htqp.fsf@gnu.org> (raw)
In-Reply-To: <83d244wwy5.fsf@gnu.org>

> From: phillip.lord@newcastle.ac.uk (Phillip Lord)
> Date: Tue, 07 Apr 2015 15:38:42 +0100
> 
> > I don't understand how could the slow-down happen here, at least not
> > due to something Emacs does.  Can you collect thread-level CPU usage,
> > and see which threads are using CPU?
> 
> How do I go about this?

Pressing 'H' in 'top' is one way; there might be others.

> > What about timers -- do you have many of them running?  What is the
> > value of timer-list and timer-idle-list?
> 
> A few, indeed, but not thousands. I know how to debug timers but not
> work out if one is chewing CPU. Some of them my own timers.

When Emacs becomes sluggish, does pressing and holding an arrow key
produces a slow response time for the first keypress, followed by more
or less normal response times for the next keypresses?  If so, the
culprit is probably some idle timer.  If all the keypresses get the
same slow response, then it could be a non-idle timer.

Showing a list of the timers you have might be a first step towards
digging into this possibility.





  reply	other threads:[~2015-04-07 14:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 14:15 bug#20134: 24.4.90; Emacs slowdown to eventual hang Phillip Lord
     [not found] ` <handler.20134.B.14266881615335.ack@debbugs.gnu.org>
2015-03-19 17:58   ` bug#20134: Acknowledgement (24.4.90; Emacs slowdown to eventual hang) Phillip Lord
2015-03-19 20:31     ` Eli Zaretskii
2015-04-07 14:56       ` Eli Zaretskii [this message]
2015-04-07 15:28         ` Phillip Lord
2015-04-07 15:37           ` Eli Zaretskii
2015-04-07 16:16             ` Phillip Lord
2015-04-07 16:23               ` Eli Zaretskii
2015-04-07 16:51             ` Phillip Lord
2015-04-07 17:30               ` Eli Zaretskii
2015-04-08  8:46                 ` Phillip Lord
2015-04-08 11:34                   ` Eli Zaretskii
2015-04-08 14:38                   ` Stefan Monnier
2015-04-08 15:55                     ` Phillip Lord
2015-04-08 16:05                       ` Eli Zaretskii
2015-04-08 16:42                         ` Phillip Lord
2015-04-08 17:08                           ` Phillip Lord
2015-04-08 17:44                             ` Eli Zaretskii
2015-04-08 17:57                               ` martin rudalics
2015-04-08 19:58                                 ` Phillip Lord
2015-05-14 12:10                               ` Phillip Lord
2020-01-23 12:59                                 ` Stefan Kangas
2020-05-15  5:33                                   ` Stefan Kangas

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=83iod8htqp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20134@debbugs.gnu.org \
    --cc=phillip.lord@newcastle.ac.uk \
    /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.