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: Sun, 15 Jan 2017 14:47:13 +0000 [thread overview]
Message-ID: <bug-99418-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99418
Bug ID: 99418
Summary: DRI3 Stuttering while scrolling in Chromium/Chrome
with VBLANK off
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: lei.pero@gmail.com
Not sure where to report this issue, as title says, problem is not present with
VBLANK enabled.
Vblank is disabled in both xorg configuration and .drirc profile (and clutter
when using GNOME).
Expected behaviour (DRI2):
When scrolling pages (with smooth scroll) in Chromium for example, it defaults
at FPS=refresh rate (my case 85Hz), there is just tearline present, everything
else is smooth and fine (as with vblank enabled, except tearline).
On DRI3 however, even on simple forums/text based pages, there is
stuttering/choppy scrolling.
GPU is HD 6770, Xorg server version is 1.19.1, if you need more
information/testing, would be happy to do it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2563 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 reply other threads:[~2017-01-15 14:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 14:47 bugzilla-daemon [this message]
2017-01-17 6:34 ` [Bug 99418] DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off 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
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.