bug#11822: 24.1; emacsclient terminal mode captures escape characters as text

[Ken Raeburn]

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