[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#61667: 29.0.60; Failure to redisplay
From: |
Dmitry Gutov |
Subject: |
bug#61667: 29.0.60; Failure to redisplay |
Date: |
Sun, 26 Feb 2023 19:00:32 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
On 26/02/2023 17:54, Gregory Heytings wrote:
To avoid this measurement affecting the delay itself, as we saw with
printfs and trace-redisplay, the timings should be sent via pipe to
a file, not to the screen.
If they indeed don't affect the measurement when they are sent to a
file, it is probably possible to sent them to the screen without
affecting the measurement, by calling 'tail -f' on the file in which
they are recorded in another terminal.
Yes, I suppose this can work, if the new terminal is positioned far
away from Emacs's window.
None of the new proposed tests depend on me being able to monitor the
output in real time, though.
If you want to measure the latency between the moment an XFlush is
issued by Emacs and the moment you actually see the buffer contents of
the buffer on screen, I think you could screencast your repro and use
the recorded video to make that measurement (unless screencasting
eliminates the problem, too...).
Its weird: screencast recording doesn't stop the problem from happening
live, but it fails to capture how it looks.
I've recorded a half dozen of such screencasts, and I think only one of
them managed to capture the desynchronization between the title bar and
the window update. The rest look like there is no delay.
But this one occurrence you can see here (attempt #4, around 00:00:06):
https://a.uguu.se/Oopgcemf.webm
- bug#61667: 29.0.60; Failure to redisplay, (continued)
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Eli Zaretskii, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Gregory Heytings, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Gregory Heytings, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay,
Dmitry Gutov <=
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/26
- bug#61667: 29.0.60; Failure to redisplay, Gregory Heytings, 2023/02/27
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/27
- bug#61667: 29.0.60; Failure to redisplay, Gregory Heytings, 2023/02/27
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/27
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/28
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/28
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/28
- bug#61667: 29.0.60; Failure to redisplay, Po Lu, 2023/02/28
- bug#61667: 29.0.60; Failure to redisplay, Dmitry Gutov, 2023/02/28