unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20134@debbugs.gnu.org
Subject: bug#20134: Acknowledgement (24.4.90; Emacs slowdown to eventual hang)
Date: Tue, 07 Apr 2015 16:28:23 +0100	[thread overview]
Message-ID: <877fto3qlk.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <83iod8htqp.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 7 Apr 2015 17:56:46 +0300")

Eli Zaretskii <eliz@gnu.org> writes:
>> 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.


I will add this tomorrow. It takes a while to produce the crash.

>> > 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?

Nope. The lag is general. If I carry one for long enough, emacs hangs
totally, but Emacs because unusable long before that point.

> 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.


timer-list is a variable defined in `C source code'.
Its value is
([nil 21795 62426 202965 60 ac-clear-variables-every-minute nil nil 1000])

timer-idle-list is a variable defined in `C source code'.
Its value is shown below.

Documentation:
List of active idle-time timers in order of increasing time.

Value: ([t 0 0 500000 t jit-lock-context-fontify nil idle 0]
 [t 0 0 500000 t
    #[0 "\205\301 \207"
        [eldoc-mode eldoc-print-current-symbol-info]
        1 "\n\n(fn)"]
    nil idle 0]
 [nil 0 1 0 t pabbrev-short-idle-timer nil idle 0]
 [nil 0 1 200000 t reftex-view-crossref-when-idle nil idle 0]
 [nil 0 5 0 t pabbrev-idle-timer-function nil idle 0]
 [nil 0 30 0 nil desktop-auto-save nil idle 0]
 [nil 0 60 0 t bibtex-parse-buffers-stealthily nil idle 0])

[back]





  reply	other threads:[~2015-04-07 15:28 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
2015-04-07 15:28         ` Phillip Lord [this message]
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

  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=877fto3qlk.fsf@newcastle.ac.uk \
    --to=phillip.lord@newcastle.ac.uk \
    --cc=20134@debbugs.gnu.org \
    --cc=eliz@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).