Commen=
t # 32
on bug 99418<=
/a>
from Michel D=C3=A4nzer
(In reply to lei.pero from comment #31)
> It's still odd behaviour, in both cases Chrome c=
aps 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 re=
ason 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 re=
fresh
> rate.
It's possible that the mutter framerate doesn't match the refresh rate (you=
can
check by setting GALLIUM_HUD=3Dfps 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 config=
uration problem in the code
> (since it happens only there), it doesn't follow configuration in .dri=
rc as
> other WM's.
Not really. By setting vblank_mode=3D0, you're forcing mutter to run in a w=
ay 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. :)