Mir

Comment 16 for bug 1665802

Revision history for this message
Alberto Aguirre (albaguirre) wrote :

3. Not sure. This is snap world, so it's cumbersome to bring profiler + deps to do the job.

4. No - I suspect because the driver can keep up with the very simple shader used in those.
5. It's not a nested server.
6. Yes mesa-kms, it's freedreno.

""It does mean we need a way to disable client side vsync for problematic drivers."
I doubt that, simply because drivers have no interest in the swap interval in use (we implement it in Mir)."

From my experiments, removing client side vsync and not using swap interval 0, resolves the issues I'm seeing. So it's a potential workaround.