From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@newcastle.ac.uk (Phillip Lord)
Cc: 20134@debbugs.gnu.org
Subject: bug#20134: Acknowledgement (24.4.90; Emacs slowdown to eventual hang)
Date: Wed, 08 Apr 2015 20:44:18 +0300 [thread overview]
Message-ID: <83wq1mfrbh.fsf@gnu.org> (raw)
In-Reply-To: <87fv8ah7jn.fsf@newcastle.ac.uk>
> From: phillip.lord@newcastle.ac.uk (Phillip Lord)
> Cc: <monnier@iro.umontreal.ca>, <20134@debbugs.gnu.org>
> Date: Wed, 08 Apr 2015 18:08:28 +0100
>
>
> Here is another backtrace.
There's that xic_set_preeditarea and xcb_wait_for_event again, called
as part of Emacs redisplaying and setting the cursor. I don't
understand why this would become progressively slower and slower
during a session, but then I know nothing about XIC.
What happens if, starting with this backtrace, you type "finish" until
it stops showing the next frame up the call-stack -- which frame does
it fail to leave from?
next prev parent reply other threads:[~2015-04-08 17:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 14:15 bug#20134: 24.4.90; Emacs slowdown to eventual hang Phillip Lord
[not found] ` <handler.20134.B.14266881615335.ack@debbugs.gnu.org>
2015-03-19 17:58 ` bug#20134: Acknowledgement (24.4.90; Emacs slowdown to eventual hang) Phillip Lord
2015-03-19 20:31 ` Eli Zaretskii
2015-04-07 14:56 ` Eli Zaretskii
2015-04-07 15:28 ` Phillip Lord
2015-04-07 15:37 ` Eli Zaretskii
2015-04-07 16:16 ` Phillip Lord
2015-04-07 16:23 ` Eli Zaretskii
2015-04-07 16:51 ` Phillip Lord
2015-04-07 17:30 ` Eli Zaretskii
2015-04-08 8:46 ` Phillip Lord
2015-04-08 11:34 ` Eli Zaretskii
2015-04-08 14:38 ` Stefan Monnier
2015-04-08 15:55 ` Phillip Lord
2015-04-08 16:05 ` Eli Zaretskii
2015-04-08 16:42 ` Phillip Lord
2015-04-08 17:08 ` Phillip Lord
2015-04-08 17:44 ` Eli Zaretskii [this message]
2015-04-08 17:57 ` martin rudalics
2015-04-08 19:58 ` Phillip Lord
2015-05-14 12:10 ` Phillip Lord
2020-01-23 12:59 ` Stefan Kangas
2020-05-15 5:33 ` Stefan Kangas
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=83wq1mfrbh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20134@debbugs.gnu.org \
--cc=phillip.lord@newcastle.ac.uk \
/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).