unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#6443: 23.2; Many files take 6-15 seconds to open after upgrade to 23.2 on WinXP
Date: Thu, 17 Jun 2010 07:04:10 -0600	[thread overview]
Message-ID: <hvd6g9$29k$1@dough.gmane.org> (raw)
In-Reply-To: <4C19A221.70909@oneroad.com>

[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]

Keith M Swartz wrote:

> Upgraded from emacs 22.3 to 23.2.1 on Windows XP SP 3, using pre-built 
> binaries from ftp.gnu.org. I've found that emacs is frequently 
> unresponsive, would hang for several seconds during routine operations, 
> including auto-save, etc. Did some searching, and found that default 
> setting for w32-get-true-file-attributes had changed, so I reverted that 
> back to nil -- this helped.
> 
> Now, at best, opening files takes about 1-2 seconds, which is 
> acceptable. But sometimes, it still takes 6-8 seconds to open files. 
> I've confirmed there is no CPU usage during this time, and Process 
> Monitor does not show enough specific information to determine whether 
> it's an I/O call it's hanging on, or what I/O call that is. Ctrl-G is 
> unresponsive and doesn't act until after control resumes. I can 
> reproduce this even with no startup files, and it happens just as often.
> 
> It APPEARED for a while that turning off font-lock-mode globally helped, 
> but I think that may be a red herring. When turning it off, the first 
> few file opens would usually go quickly, but after that, opening a file 
> from a new location would bring back the 6-8 second hang. Not EVERY file 
> opens this slowly, but enough do that it definitely interrupts the work 
> flow.
> 
> All of my operations are happening locally, and not on a network drive. 
> I have a network drive defined, but even when the drive is not mounted, 
> the hangs still occur.
> 
> I have AV software installed, but can't disable it (due to corporate 
> settings) -- however, I haven't seen this problem manifest in any other 
> program, so I'm hesitant to blame that.
> 
> I am working on testing with another machine to see if I can reproduce, 
> but advice on key differences to look for would be helpful.

Try this on each machine: (elp-instrument-file "/files\\.elc\\'")

Then visit a file, and M-x elp-results.

You'll need the attached helper function.

-- 
Kevin Rodgers
Denver, Colorado, USA

[-- Attachment #2: elp-instrument-file.el --]
[-- Type: application/emacs-lisp, Size: 521 bytes --]

  reply	other threads:[~2010-06-17 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  4:18 bug#6443: 23.2; Many files take 6-15 seconds to open after upgrade to 23.2 on WinXP Keith M Swartz
2010-06-17 13:04 ` Kevin Rodgers [this message]
2011-09-21 20:39   ` Lars Magne Ingebrigtsen
2011-10-06  5:53     ` Kevin Rodgers
2011-10-06 19:11       ` Lars Magne Ingebrigtsen

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='hvd6g9$29k$1@dough.gmane.org' \
    --to=kevin.d.rodgers@gmail.com \
    --cc=bug-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 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).