From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: <help-gnu-emacs@gnu.org>
Subject: Re: Emacs Slowdown
Date: Thu, 12 Mar 2015 11:36:43 +0000 [thread overview]
Message-ID: <87lhj2qwfo.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <87pp8i75nk.fsf@newcastle.ac.uk> (Phillip Lord's message of "Mon, 9 Mar 2015 11:48:47 +0000")
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.
This bit of trace above was what was confusing me, as I couldn't see why
there were so many calls to ido-find-file, or the time taken in
ad-Advice-call-interactively. Actually most of this seems to be coming
from ido-ubiquitous.el which advinces call-interactively. Certainly the
problem goes away without ido-ubiquitous.
I haven't worked out yet whether there is a specific problem with
ubiquitous yet, or whether it really is leaking memory. Or whether, it's
just the nature of the beast.
Phil
next prev parent reply other threads:[~2015-03-12 11:36 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 [this message]
2015-03-16 11:41 ` Phillip Lord
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhj2qwfo.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.
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.