<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Very slow rendering on ASUS Nexus 7, ARM, Tegra 3" href="https://bugs.freedesktop.org/show_bug.cgi?id=56891#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Very slow rendering on ASUS Nexus 7, ARM, Tegra 3" href="https://bugs.freedesktop.org/show_bug.cgi?id=56891">bug 56891</a> from <a class="email" href="mailto:marmvta@gmail.com" title="marmuta <marmvta@gmail.com>"> marmuta</a> <pre>Hmm, there shouldn't actually be more than five or so nesting levels, the first probably being GTK's double buffering. How can I read the levels from the trace? I assumed it somehow repeats at Observing '/home/ubuntu/onboard.trace'...., are those nesting levels too? Most of the nesting happens only occasianally, i.e. on startup, resizing, etc. and is then masked to the main context all other times. Drawing all the keys at once with shadows and gradients turned out too slow even on non-mobile devices, hence all that caching. Driver quality is what I'm afraid of. Would that explain why the image backends in the first attachment are so much faster than cairo-xlib?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>