Subject: bug#61667: 29.0.60; Failure to redisplay

From: Eli Zaretskii <[email-masked]>
Date: Sat, 25 Feb 2023 09:12:14 +0200

> Date: Fri, 24 Feb 2023 23:49:05 +0200
> Cc: [email-masked], [email-masked], [email-masked]
> From: Dmitry Gutov <[email-masked]>
> 
> On 24/02/2023 23:19, Eli Zaretskii wrote:
> >> Date: Fri, 24 Feb 2023 23:03:12 +0200
> >> Cc:[email-masked],[email-masked],[email-masked]
> >> From: Dmitry Gutov<[email-masked]>
> >>
> >> +int64_t now_millis() {
> >> +  struct timespec now;
> >> +  timespec_get(&now, TIME_UTC);
> >> +
> >> +  return ((int64_t) now.tv_sec) * 1000 + ((int64_t) now.tv_nsec) / 1000;
> >                                                                        ^^^^
> > That 1000 should be 1000000, right?
> 
> Right, sorry. I misread it in the doc for "microseconds".
> 
> The result makes no difference, though: now only zeros are printed (and 
> sometimes 1):
> 
> [x_set_name] time to x_set_name_internal: 0
> [x_set_name] time to x_set_name_internal: 0

Well, 1 msec is a far cry from 20 or 50...

> So the calls take < 1ms.

Yes.  Which means these X and GTK calls are not the direct culprit of
the delay.