From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: <help-gnu-emacs@gnu.org>
Subject: Re: Emacs Slowdown
Date: Mon, 16 Mar 2015 11:41:09 +0000 [thread overview]
Message-ID: <87r3sp6uga.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <87lhj2qwfo.fsf@newcastle.ac.uk> (Phillip Lord's message of "Thu, 12 Mar 2015 11:36:43 +0000")
Phillip Lord <phillip.lord@newcastle.ac.uk> writes:
> Phillip Lord <phillip.lord@newcastle.ac.uk> writes:
>
>> - command-execute 3996 73%
>> - call-interactively 3996 73%
>> - apply 3996 73%
>> - ad-Advice-call-interactively 3996 73%
>> - #<subr call-interactively> 3993 73%
>> - ido-find-file 2231 40%
>> - ido-file-internal 2231 40%
>> - ido-read-internal 2181 39%
>> - apply 2181 39%
>> - ad-Advice-ido-read-internal 2181 39%
>> + #<compiled 0xce6205>
>
>
>
> Okay, I think that I have chased down the issue here (at least to a
> first approximation.
>
> Certainly the problem goes away without ido-ubiquitous.
Okay, I may have been premature here. I am still getting slowdown
anyway. Here is the top level of a longish profile (difficult to do
because Emacs is so slow that it's hard to type).
Slight worried that one of my own packages is in the list although, it's
does not appear to be called often. To my knowledge I didn't actually
drag-region during this period, so am confused about this. This emacs
hung eventually and had to be xkill'd.
- command-execute 20646 93%
- call-interactively 20643 93%
- mouse-drag-region 15591 70%
- mouse-drag-track 15591 70%
- eval 15474 69%
- track-mouse 15471 69%
- funcall 12410 55%
- #<compiled 0x5d65117> 12410 55%
- read-event 12379 55%
- redisplay_internal (C function) 62 0%
+ #<compiled 0x40a92d> 30 0%
and 19 0%
- msb-menu-bar-update-buffers 13 0%
- msb--create-buffer-menu 13 0%
- msb--create-buffer-menu-2 13 0%
msb--mode-menu-cond 13 0%
- mouse-set-point 110 0%
- posn-set-point 110 0%
- select-window 110 0%
- run-hooks 110 0%
- lentic-mode-buffer-list-update-hook 110 0%
- if 110 0%
- -map 110 0%
- mapcar 110 0%
+ #<lambda 0x2aa4c8f82b1b222c> 110 0%
+ byte-code 3163 14%
+ list 1360 6%
+ Info-mouse-follow-nearest-node 213 0%
+ Info-index 113 0%
+ next-line 45 0%
+ info 33 0%
+ previous-line 31 0%
+ save-buffer 23 0%
+ Info-index-next 18 0%
+ newline 13 0%
+ execute-extended-command 11 0%
+ mouse-set-point 8 0%
+ move-end-of-line 5 0%
+ paredit-close-round 5 0%
+ indent-for-tab-command 4 0%
+ paredit-open-round 3 0%
self-insert-command 1 0%
- ...
next prev parent reply other threads:[~2015-03-16 11:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 11:48 Emacs Slowdown Phillip Lord
2015-03-09 16:16 ` Eli Zaretskii
2015-03-09 21:50 ` Stefan Monnier
2015-03-10 12:37 ` Phillip Lord
2015-03-10 19:00 ` Eli Zaretskii
2015-03-09 21:59 ` Stefan Monnier
2015-03-10 12:39 ` Phillip Lord
2015-03-10 13:22 ` Stefan Monnier
2015-03-12 11:36 ` Phillip Lord
2015-03-16 11:41 ` Phillip Lord [this message]
2015-03-16 12:36 ` Stefan Monnier
2015-03-16 16:51 ` Phillip Lord
2015-03-18 12:23 ` Phillip Lord
2015-03-18 12:44 ` Stefan Monnier
2015-03-18 14:13 ` Phillip Lord
2015-03-18 14:53 ` Stefan Monnier
2015-03-18 16:34 ` Phillip Lord
2015-03-18 16:32 ` Eli Zaretskii
2015-03-18 17:04 ` Phillip Lord
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=87r3sp6uga.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--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).