unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Sokoloski <asokoloski@gmail.com>
To: 21144@debbugs.gnu.org
Subject: bug#21144: Performance problem with certain text editing operations (emacs 24.4.1)
Date: Mon, 27 Jul 2015 16:57:08 +0100	[thread overview]
Message-ID: <CAAajcW68R25dJfRwzYoCX00cv5Tkc2Eog4ba+pr8+ZBQm-moJQ@mail.gmail.com> (raw)

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

Hi folks,

I've run into something that I can't figure out.  Emacs 24.4.1 usually
hangs for a short time (on the order of a second) when I do one of these
things:

1) Kill a line
2) Kill a region
3) run kill-ring save

It seems to be slow to do anything that copies text to the kill ring.
Occasionally it seems like something I do (can't figure out what) makes it
temporarily fast again, but then gradually slow down again until it takes
about 1 second.  It doesn't happen all the time, but when it happens it
happens pretty reliably.

The -q option does not make any difference.  Font-lock-mode doesn't make
any difference, nor does the size of the buffer seem to.

Nothing exciting seems to show up under profiling -- the big cpu users are
just the profiling stuff like the report.  Also, setting debug-on-quit and
pressing ctrl-g during the lag doesn't make the debugger pop up.

However, I can't seem to reproduce the lag when running with -nw, so maybe
it's something with the windowing.

I'm running debian jesse, with awesome window manager version v3.4.15.

As you can imagine, this is pretty distracting, so I'd appreciate any help
anyone can provide!

Thanks in advance,
Aaron

[-- Attachment #2: Type: text/html, Size: 1516 bytes --]

             reply	other threads:[~2015-07-27 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 15:57 Aaron Sokoloski [this message]
2016-08-10  1:10 ` bug#21144: Performance problem with certain text editing operations (emacs 24.4.1) npostavs
2016-12-07 21:04   ` Glenn Morris

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=CAAajcW68R25dJfRwzYoCX00cv5Tkc2Eog4ba+pr8+ZBQm-moJQ@mail.gmail.com \
    --to=asokoloski@gmail.com \
    --cc=21144@debbugs.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).