WebRender in Firefox is pretty sick but it has a really egregious vsync timing problem where it periodically drops to 30hz and it's like nails on a chalkboard, I just can't handle it. My eyes are broken
-
-
Replying to @antumbral
What platform? (BTW, this is probably the fault of Gecko’s nsRefreshDriver, not WebRender. WebRender knows nothing about timing itself and only composites when Gecko asks it to.)
2 replies 0 retweets 4 likes -
Replying to @pcwalton
win10 x64, geforce 1080. I filed a bug already, and have other refresh timing related issues on this rig anyway. It just only showed up when I switched to nightly+WR. Maybe due to different GPU load profile?
1 reply 0 retweets 0 likes -
-
Replying to @pcwalton
is it worth trying the ol' 'disable gpu power management' trick and seeing if that makes a difference? I know Chrome's compositor and scheduling logic literally could not handle gpu clock changes for a good year+
1 reply 0 retweets 0 likes -
Replying to @antumbral
Sure, go for it. I don’t know much about OS composition on Windows though…
1 reply 0 retweets 0 likes -
Replying to @pcwalton
this only influences the actual clock time spent rasterizing on the GPU, but that can have an impact on pipeline stuff like if scheduling is done based on how long the last paint took? I don't know the pipeline for this stuff in gecko at all.
1 reply 0 retweets 0 likes -
Replying to @antumbral @pcwalton
It was bad in Chrome because they had a broken implementation of backpressure, so if a frame took too long (say, 17ms) because the GPU hadn't clocked up, chrome would drop to 30hz right before the GPU clocked up to make it possible to hit 60 with the same workload
1 reply 0 retweets 0 likes -
Replying to @antumbral @pcwalton
incidentally, text looks great in nightly w/webrender turned on. i'm sure this is placebo and it's actually still using directwrite, but if it's not placebo: yay
1 reply 0 retweets 0 likes -
Replying to @antumbral
Yeah, it’s still using DirectWrite. Pathfinder will be coming, but we gotta ship WR first before we start dealing with driver bugs involving floating point render targets…
1 reply 0 retweets 0 likes
(Note that the code to use Pathfinder is in the repo, it just isn’t enabled yet)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.