GNU bug report logs - #21473
24.5; very slow tooltip display to sort-of-slow remote display

Previous Next

Full log

Message #20 received at 21473 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ken Raeburn <raeburn <at> permabit.com>
Cc: 21473 <at> debbugs.gnu.org
Subject: Re: bug#21473: 24.5;
 very slow tooltip display to sort-of-slow remote display
Date: Sun, 27 Sep 2015 13:38:24 +0300

> From: Ken Raeburn <raeburn <at> permabit.com>
> Date: Sun, 27 Sep 2015 06:35:30 -0400
> Cc: 21473 <at> debbugs.gnu.org
> 
> This one’s still basically unchanged. I just got 165 _XReply round-trip delays, with face realization color requests accounting for 60 of those, x_create_tip_frame initialization using “black” and “white” accounting for a dozen more, and other XParseColor or XAllocColor calls bringing it up to around 100 (maybe fewer than last time, by just a few); 38 XSync calls, almost all for error catching. The other ~20% is XQueryColors, XListFonts, XGetWindowProperty, and a few other calls that need responses.

So you are saying that creating a tip frame is significantly different
in this regard from creating any "regular" frame?  If so, where are
the differences, wrt face realization and color allocation?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.