<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off" href="https://bugs.freedesktop.org/show_bug.cgi?id=99418#c35">Comment # 35</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off" href="https://bugs.freedesktop.org/show_bug.cgi?id=99418">bug 99418</a> from <a class="email" href="mailto:lei.pero@gmail.com" title="lei.pero@gmail.com">lei.pero@gmail.com</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=99418#c34">comment #34</a>) > (In reply to lei.pero from <a href="show_bug.cgi?id=99418#c33">comment #33</a>) > > Yeah, but by setting 1 and using any other WM results in Chromium/Chrome > > being VSYNC-ed, [...] > > With a compositing manager, tearing or not is up to that. > > > > [...] i would call it mutter/clutter configuration bug [...] > > vblank_mode is Mesa configuration overriding mutter's intent, so it cannot > reasonably be called that. > Well, whatever it is, it affects only mutter/mutter based WM's, for now, workaround is to use vblank_mode value "1". > > > plus it doesn't explain DRI2 behavior that follows same standard :). > > It's probably just a happy accident that it works better according to your > criteria with DRI2. Or unhappy accident for DRI3 :).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>