Comment 25 for bug 1550371

And based on John's earlier remark, ie that the same HW and drivers do
perform properly with another OS, then it means that Ubuntu components
between apps and driver/HW are introducing that extra 20/40ms delay. Mir?
Unity8? Something else?

On Tue, Apr 19, 2016 at 8:47 PM, Chris Coulson <email address hidden>
wrote:

> The main reason Oxide is slow is because the browser's UI thread is
> being blocked for long periods of time due to an issue *outside* of
> Oxide.
>
> As a quick test, I just ran the address book app with
> QSG_RENDER_TIMING=1, and it demonstrates exactly the same issue as the
> browser - the render thread regularly being blocked for over 20ms and
> sometimes up to 40ms in eglSwapBuffers, which causes the UI thread to be
> blocked, eg:
>
> qt.scenegraph.time.renderloop: Frame rendered with 'threaded' renderloop
> in 41ms, sync=0, render=5, swap=35 - (on render thread)
> qt.scenegraph.time.renderloop: Frame prepared with 'threaded' renderloop,
> polish=0, lock=0, blockedForSync=36, animations=0 - (on Gui thread)
> QQuickView(0x385ef0)
>
> Scrolling in address book app is also very janky (like with every other
> app and the shell on my M10). I'm not the only person seeing this, am I?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1550371
>
> Title:
> Webbrowser slow scroll and artifact rendering on freiza
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1550371/+subscriptions
>