GNU bug report logs -
#21144
Performance problem with certain text editing operations (emacs 24.4.1)
Previous Next
Reported by: Aaron Sokoloski <asokoloski <at> gmail.com>
Date: Mon, 27 Jul 2015 16:00:03 UTC
Severity: normal
Tags: moreinfo, wontfix
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21144 in the body.
You can then email your comments to 21144 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21144
; Package
emacs
.
(Mon, 27 Jul 2015 16:00:04 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Aaron Sokoloski <asokoloski <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 27 Jul 2015 16:00:06 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#21144
; Package
emacs
.
(Wed, 10 Aug 2016 01:11:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 21144 <at> debbugs.gnu.org (full text, mbox):
tags 21144 moreinfo
quit
Aaron Sokoloski <asokoloski <at> gmail.com> writes:
> 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!
Do you still see this with more recent Emacs? If yes, are you running
any kind of daemon that monitors the clipboard? The symptoms sound a
bit like http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24013 "[KDE/Plasma
5] Emacs 25.x uses up all memory and needs to be killed".
Also, if you can add the details that report-emacs-bug usually gives,
whether you're using gtk or lucid toolkit could be significant.
Added tag(s) moreinfo.
Request was from
npostavs <at> users.sourceforge.net
to
control <at> debbugs.gnu.org
.
(Wed, 10 Aug 2016 01:11:02 GMT)
Full text and
rfc822 format available.
Added tag(s) wontfix.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Wed, 07 Dec 2016 21:05:01 GMT)
Full text and
rfc822 format available.
Reply sent
to
Glenn Morris <rgm <at> gnu.org>
:
You have taken responsibility.
(Wed, 07 Dec 2016 21:05:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Aaron Sokoloski <asokoloski <at> gmail.com>
:
bug acknowledged by developer.
(Wed, 07 Dec 2016 21:05:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 21144-done <at> debbugs.gnu.org (full text, mbox):
npostavs <at> users.sourceforge.net wrote:
> Do you still see this with more recent Emacs? If yes, are you running
> any kind of daemon that monitors the clipboard? The symptoms sound a
> bit like http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24013 "[KDE/Plasma
> 5] Emacs 25.x uses up all memory and needs to be killed".
>
> Also, if you can add the details that report-emacs-bug usually gives,
> whether you're using gtk or lucid toolkit could be significant.
No response in months, closing.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 05 Jan 2017 12:24:10 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 172 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.