From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99418] DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off
Date: Fri, 20 Jan 2017 03:28:05 +0000 [thread overview]
Message-ID: <bug-99418-502-T0fDfJWLs5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99418-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 927 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99418
--- Comment #17 from Michel Dänzer <michel@daenzer.net> ---
(In reply to lei.pero from comment #14)
> It does happen on modesetting driver regardless of DRI version, strange.
The modesetting driver doesn't allow disabling DRI3 on the server side. You can
always disable it on the client side though with the environment variable
LIBGL_DRI3_DISABLE=1 .
The fps graph shows the same framerate in both videos, so the problem seems
rather about animation timing. It might be related to the fact that DRI3 allows
triple buffering, and might be at least partially an application issue. It
would be interesting though if it also happens with a non-AMD GPU.
BTW, is there any particular reason why you're disabling sync-to-vblank? It is
the intended mechanism for smooth animation...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1815 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-20 3:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 14:47 [Bug 99418] DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off bugzilla-daemon
2017-01-17 6:34 ` bugzilla-daemon
2017-01-17 8:11 ` bugzilla-daemon
2017-01-17 8:11 ` bugzilla-daemon
2017-01-17 8:12 ` bugzilla-daemon
2017-01-17 8:14 ` bugzilla-daemon
2017-01-18 8:32 ` bugzilla-daemon
2017-01-18 8:32 ` bugzilla-daemon
2017-01-18 8:40 ` bugzilla-daemon
2017-01-18 10:51 ` bugzilla-daemon
2017-01-18 11:02 ` bugzilla-daemon
2017-01-18 11:03 ` bugzilla-daemon
2017-01-18 11:04 ` bugzilla-daemon
2017-01-18 11:11 ` bugzilla-daemon
2017-01-18 11:11 ` bugzilla-daemon
2017-01-19 8:12 ` bugzilla-daemon
2017-01-19 15:40 ` bugzilla-daemon
2017-01-19 15:41 ` bugzilla-daemon
2017-01-19 15:42 ` bugzilla-daemon
2017-01-20 3:28 ` bugzilla-daemon [this message]
2017-01-20 11:00 ` bugzilla-daemon
2017-01-20 18:59 ` bugzilla-daemon
2017-01-20 19:05 ` bugzilla-daemon
2017-01-23 9:24 ` bugzilla-daemon
2017-01-23 14:35 ` bugzilla-daemon
2017-01-24 8:30 ` bugzilla-daemon
2017-01-24 20:41 ` bugzilla-daemon
2017-01-25 8:30 ` bugzilla-daemon
2017-01-25 12:28 ` bugzilla-daemon
2017-01-26 1:21 ` bugzilla-daemon
2017-01-26 14:38 ` bugzilla-daemon
2017-02-01 22:17 ` bugzilla-daemon
2017-02-02 1:45 ` bugzilla-daemon
2017-02-02 3:43 ` bugzilla-daemon
2017-02-02 4:00 ` bugzilla-daemon
2017-02-02 4:17 ` bugzilla-daemon
2017-02-02 5:56 ` bugzilla-daemon
2017-02-02 6:19 ` bugzilla-daemon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99418-502-T0fDfJWLs5@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox