Comment 23 for bug 1550371

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?