unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Bryan Gilbert <bryan@bryan.sh>, Eli Zaretskii <eliz@gnu.org>
Cc: 28695@debbugs.gnu.org
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Thu, 5 Oct 2017 16:36:53 +0300	[thread overview]
Message-ID: <1931afeb-51cb-89c9-72ff-c8a062fecba7@yandex.ru> (raw)
In-Reply-To: <874lrfcg4s.fsf@bryan.sh>

On 10/4/17 2:21 PM, Bryan Gilbert wrote:

>> Isn't it strange that only some people see these problems, while
>> others (the majority?) are very happy with double-buffering?  Could it
>> be that the problems are triggered by some specific system
>> configurations or Emacs build-time features?  If so, we could perhaps
>> turn it off only for those configurations, because people who are
>> happy with this are extremely happy, and will probably be disappointed
>> if we just turn it off globally.

Eli, perhaps it would be wise to ask the reporter if he'd like it to be 
turned off by default, if this problem can't be fixed in time.

Personally, I can stand a few minor glitches, given that double 
buffering saves me from flickering, which has been an annoyance for years.

> I'm currently using a Dell XPS 15 laptop with a 4K display and running
> at a resolution of 3840x2160.

Bryan, which revision/year is it? I also have an XPS 15 (with Skylake 
CPU) with 4K resolution, and at worst, I see the minor stutters you show 
in the 1080p video (after adding the advice, yes).

Ubuntu 17.04 with Unity 7 here.

I wasn't able to compare with the revision before double buffering, 
though: after checking out c29071587c64efb30792bd72248d3c791abd9337^, 
./autogen.sh says:

Checking whether you have the necessary tools...
(Read INSTALL.REPO for more details on building Emacs)
Checking for autoconf (need at least version 2.65)...
ok
Checking for automake (need at least version 1.11)...
ok
Your system has the required tools.
Running 'autoreconf -fi -I m4' ...
/usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No 
such file or directory
/usr/bin/m4:aclocal.m4:12: cannot open `m4/d-type.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:20: cannot open `m4/explicit_bzero.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:46: cannot open `m4/localtime-buffer.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:52: cannot open `m4/minmax.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:55: cannot open `m4/mode_t.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:58: cannot open `m4/nstrftime.m4': No such file 
or directory
/usr/bin/m4:aclocal.m4:60: cannot open `m4/open-cloexec.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:61: cannot open `m4/open.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:103: cannot open `m4/unlocked-io.m4': No such 
file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
/usr/bin/m4:aclocal.m4:9: cannot open `m4/count-leading-zeros.m4': No 
such file or directory
/usr/bin/m4:aclocal.m4:12: cannot open `m4/d-type.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:20: cannot open `m4/explicit_bzero.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:46: cannot open `m4/localtime-buffer.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:52: cannot open `m4/minmax.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:55: cannot open `m4/mode_t.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:58: cannot open `m4/nstrftime.m4': No such file 
or directory
/usr/bin/m4:aclocal.m4:60: cannot open `m4/open-cloexec.m4': No such 
file or directory
/usr/bin/m4:aclocal.m4:61: cannot open `m4/open.m4': No such file or 
directory
/usr/bin/m4:aclocal.m4:103: cannot open `m4/unlocked-io.m4': No such 
file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
autoreconf: /usr/bin/autoconf failed with exit status: 1





  parent reply	other threads:[~2017-10-05 13:36 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
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 [this message]
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=1931afeb-51cb-89c9-72ff-c8a062fecba7@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=28695@debbugs.gnu.org \
    --cc=bryan@bryan.sh \
    --cc=eliz@gnu.org \
    /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).