[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61667: 29.0.60; Failure to redisplay
From: |
Eli Zaretskii |
Subject: |
bug#61667: 29.0.60; Failure to redisplay |
Date: |
Wed, 22 Feb 2023 19:07:43 +0200 |
> Date: Wed, 22 Feb 2023 18:24:43 +0200
> Cc: 61667@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@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?
- bug#61667: 29.0.60; Failure to redisplay, (continued)
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/23
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/23
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/23
- bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Gregory Heytings, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/24
- bug#61667: 29.0.60; Failure to redisplay,
Eli Zaretskii <=
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/22
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/22
- bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/23
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/22
bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/21