<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#c32">Comment # 32</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:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to lei.pero from <a href="show_bug.cgi?id=99418#c31">comment #31</a>) > It's still odd behaviour, in both cases Chrome caps FPS to refresh rate (this > case 85FPS), Sounds like Chrome just has its own framerate throttling which works independently from sync-to-vblank. > but using DRI3 using mutter/clutter, for some reason it creates > continuous stutters, even tho FPS is the same and all other parameters are > equal. It really looks (when viewed live) as if FPS is not equal to refresh > rate. It's possible that the mutter framerate doesn't match the refresh rate (you can check by setting GALLIUM_HUD=fps for the mutter process), but it's also possible it's simply due to unfortunate interaction between the Chrome and mutter frame timings. > [...] it is still probably mutter/clutter configuration problem in the code > (since it happens only there), it doesn't follow configuration in .drirc as > other WM's. Not really. By setting vblank_mode=0, you're forcing mutter to run in a way it doesn't intend. If doing so breaks something, that can hardly be considered a mutter bug, and you get to keep all the pieces. :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>