From: martin rudalics <rudalics@gmx.at>
To: Bryan Gilbert <bryan@bryan.sh>, 28695@debbugs.gnu.org
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Wed, 04 Oct 2017 11:04:49 +0200 [thread overview]
Message-ID: <59D4A431.7010801@gmx.at> (raw)
In-Reply-To: <8760bvd2w7.fsf@bryan.sh>
> I was able to verify that reverting to the previous commit before
> double-buffering was added completely removed the problem. I've made two
> short screencasts, one before the double-buffer commit and the other
> after.
Unless this problem (and that of Bug#28652) get fixed, we should either
disable double buffering by default or add some special warning so users
do not have to spend their time investigating this issue.
martin
next prev parent reply other threads:[~2017-10-04 9:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 3:10 bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2017-10-04 7:53 ` Eli Zaretskii
2017-10-04 9:04 ` martin rudalics [this message]
2017-10-04 9:32 ` Eli Zaretskii
2017-10-04 11:21 ` Bryan Gilbert
2017-10-04 11:36 ` Eli Zaretskii
2017-10-04 12:02 ` Bryan Gilbert
2017-10-04 12:31 ` Eli Zaretskii
2017-10-05 13:36 ` Dmitry Gutov
2017-10-05 14:01 ` Eli Zaretskii
2017-10-05 14:02 ` Noam Postavsky
2017-10-07 7:53 ` Dmitry Gutov
2017-10-07 8:14 ` Eli Zaretskii
2017-10-09 13:53 ` Dmitry Gutov
2017-10-09 14:03 ` Eli Zaretskii
2017-10-15 22:55 ` Dmitry Gutov
2017-10-16 2:30 ` Eli Zaretskii
2017-10-26 23:19 ` Dmitry Gutov
2017-10-28 9:33 ` Eli Zaretskii
2017-10-28 21:47 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on GNU/Linux Richard Stallman
2017-10-05 14:26 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2022-04-23 13:46 ` Lars Ingebrigtsen
2022-05-22 11:28 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59D4A431.7010801@gmx.at \
--to=rudalics@gmx.at \
--cc=28695@debbugs.gnu.org \
--cc=bryan@bryan.sh \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).