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
Sure, go for it. I don’t know much about OS composition on Windows though…
-
-
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.
-
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
- 3 more replies
New conversation -
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.