GNU bug report logs - #61667
29.0.60; Failure to redisplay

Previous Next

Full log

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

From: Po Lu <Luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 61667 <at> debbugs.gnu.org
Subject: Re: bug#61667: 29.0.60; Failure to redisplay
Date: Thu, 23 Feb 2023 06:36:54 +0800

That won't work, unfortunately -- this needs to check whether or not a function is being called at all, and not just the value of some flags at the time we update the frame title.

This is a bit of a stab in the dark, but: Dimitry, what if you make x_flush_dirty_back_buffer_on return immediately, without performing a buffer flip?

On February 23, 2023 1:07:43 AM GMT+08:00, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Wed, 22 Feb 2023 18:24:43 +0200
>> Cc: 61667 <at> debbugs.gnu.org
>> From: Dmitry Gutov <dgutov <at> yandex.ru>
>> 
>> > Careful with printfs, since we know this problem goes away when there
>> > are too many of them.  Use fputs whenever you can, since fprintf can
>> > be much more expensive.
>> 
>> Indeed, I haven't managed to reproduce the problem even once when the 
>> printing patch is applied.
>> 
>> I've  also tried this one, with the same lack of success:
>
>Maybe instead of printing to stderr, we could display something in the
>frame title, which is being updated in this scenario?  AFAIU, the
>suggested printfs just show a couple of boolean flags?

Previous Next

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