From: Ken Raeburn <raeburn@permabit.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 11822@debbugs.gnu.org
Subject: bug#11822: 24.1; emacsclient terminal mode captures escape characters as text
Date: Wed, 23 Sep 2015 16:59:07 -0400 [thread overview]
Message-ID: <6e8u7wzwbo.fsf@just-testing.permabit.com> (raw)
In-Reply-To: <5602E9AC.2070209@gmx.at> (martin rudalics's message of "Wed, 23 Sep 2015 20:04:28 +0200")
martin rudalics <rudalics@gmx.at> writes:
>> It's still not what I would call "fast", though, usually taking a couple of
>> seconds... but a cursory investigation is so far pointing the finger at
>> garbage collection being triggered during frame creation, more often than
>> not. If I raise gc-cons-threshold by a factor of 10, frame creation and
>> display is fairly quick (presumably only 90-95% of the time). The C stack
>> traces from the garbage collection calls are pretty boring (maybe_gc gets
>> called from Ffuncall which gets called from exec_byte_code etc); the Lisp
>> backtraces point the finger mostly at internal-face-x-get-resource as the
>> function being entered when GC gets invoked.
>
> See also
>
> http://lists.gnu.org/archive/html/emacs-devel/2015-07/msg00426.html
Ah, useful info on the profiler, thanks! I'm working on a 64-bit system,
so the WIDE_INT issues shouldn't be a factor, but if it's counting the
non-GC-able memory we're allocating, it's less useful than I was hoping.
Eli's suggestion of a watchpoint on consing_since_gc looks more useful.
I'll give that a try and see what comes up.
It sounds like your tooltip GC issue and my regular-frame GC issue are
probably the same or very nearly....
Ken
next prev parent reply other threads:[~2015-09-23 20:59 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 0:08 bug#11822: 24.1; emacsclient terminal mode captures escape characters as text Ken Raeburn
2012-06-30 5:55 ` Eli Zaretskii
2012-07-31 21:06 ` Ken Raeburn
2012-08-08 3:13 ` Ken Raeburn
2012-08-08 4:52 ` Dan Nicolaescu
2012-08-08 9:26 ` Ken Raeburn
2012-08-09 21:12 ` Ken Raeburn
2012-08-10 6:16 ` Eli Zaretskii
2012-08-10 7:27 ` Ken Raeburn
2012-08-10 7:46 ` Eli Zaretskii
2012-08-10 8:08 ` Eli Zaretskii
2015-09-07 21:09 ` Ken Raeburn
2015-09-08 1:29 ` Stefan Monnier
2015-09-08 4:29 ` Eli Zaretskii
2015-09-08 6:53 ` Ken Raeburn
2015-09-08 13:03 ` Stefan Monnier
2015-09-08 13:11 ` Stefan Monnier
2015-09-08 17:21 ` Eli Zaretskii
2015-09-08 4:48 ` Eli Zaretskii
2015-09-08 10:15 ` Ken Raeburn
2015-09-08 13:35 ` Stefan Monnier
2015-09-08 17:33 ` Eli Zaretskii
2015-09-08 19:54 ` Ken Raeburn
2015-09-09 14:16 ` Eli Zaretskii
2015-09-10 6:59 ` Ken Raeburn
2015-09-10 15:36 ` Eli Zaretskii
2015-09-10 17:56 ` Stefan Monnier
2015-09-10 18:06 ` Eli Zaretskii
2015-09-11 12:56 ` Stefan Monnier
2015-09-11 13:53 ` Eli Zaretskii
2015-09-11 16:53 ` Stefan Monnier
2015-09-11 6:54 ` Ken Raeburn
2015-09-11 7:22 ` Eli Zaretskii
2015-09-11 23:11 ` Ken Raeburn
2015-09-12 0:51 ` Stefan Monnier
2015-09-12 1:34 ` Ken Raeburn
2015-09-15 14:29 ` Eli Zaretskii
2015-09-15 16:14 ` Stefan Monnier
2015-09-18 14:19 ` Eli Zaretskii
2015-09-21 9:23 ` Ken Raeburn
2015-09-21 9:44 ` Eli Zaretskii
2015-09-23 17:27 ` Ken Raeburn
2015-09-23 18:04 ` martin rudalics
2015-09-23 20:59 ` Ken Raeburn [this message]
2015-09-23 19:17 ` Eli Zaretskii
2015-09-24 8:52 ` Ken Raeburn
2015-09-24 18:46 ` Eli Zaretskii
2015-09-24 20:08 ` Ken Raeburn
2015-09-25 6:49 ` Eli Zaretskii
2015-09-25 12:07 ` Stefan Monnier
2015-09-26 7:01 ` Eli Zaretskii
2015-09-25 6:50 ` Eli Zaretskii
2015-09-25 12:09 ` Stefan Monnier
2015-09-25 13:29 ` Eli Zaretskii
2015-09-25 15:18 ` Stefan Monnier
2015-09-12 7:30 ` Eli Zaretskii
2015-09-11 13:39 ` Stefan Monnier
2015-09-11 14:01 ` Eli Zaretskii
2015-09-08 13:22 ` Stefan Monnier
2015-09-08 17:25 ` Eli Zaretskii
2015-09-08 18:52 ` Stefan Monnier
2015-09-08 19:08 ` Eli Zaretskii
2015-09-08 20:37 ` Stefan Monnier
2015-09-08 17:36 ` Eli Zaretskii
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=6e8u7wzwbo.fsf@just-testing.permabit.com \
--to=raeburn@permabit.com \
--cc=11822@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
/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).