<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#c31">Comment # 31</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#c30">comment #30</a>) > (In reply to lei.pero from <a href="show_bug.cgi?id=99418#c29">comment #29</a>) > > Just want to add few things, did reported bug to gnome project, but, problem > > does not happen when "vblank_mode" value in .drirc configuration file is set > > to 1 (instead of 0 I've used before). > > 1 means sync-to-vblank is disabled by default, but the application can > enable it explicitly. 0 means sync-to-vblank is disabled regardless of what > the application wants. So this could actually be considered a configuration > issue instead of a bug anywhere. Yeah, I realized that, It's still odd behaviour, in both cases Chrome caps FPS to refresh rate (this case 85FPS), 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. Just wanted to inform you guys on this, 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>