Correction: Mir 0.21.1 does not exist yet, but it might in future.
** Changed in: mir/0.21
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
rather it was a point release
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on freiza
Status in
this should have been marked ota10
** Changed in: mir (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: mir/0.21
Status: Fix Committed => Fix Released
** Changed in: mir/0.20
Status: Fix Committed => Fix Released
** Changed in: mir (Ubuntu)
Status: Fix
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on
TLDR:
The fix was the same as bug 1563287. So you can refer to bug 1563287 to see the
history.
** Changed in: mir
Assignee: (unassigned) => Kevin DuBois (kdub)
** No longer affects: mir/0.22
** Branch linked: lp:~kdub/mir/avert-1563287
** Branch unlinked: lp:mir/0.22
** Also affects:
OK, after quite a bit of research the bottom line is that this is a mali quirk.
There are 2 potential ways both are by specification allowed to sync with the
driver - which resulted in a performance issue (covered by this bug) and a
"correctness issue" covered by bug 1573014
The performance
I don't have any measured data for the scrolling improvement - I can
probably do a chrome://tracing/ run again though
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
You will also want this smoothness fix if you're using touch:
https://code.launchpad.net/~vanvugt/unity8/fix-1556763/+merge/288891
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
thanks for that feedback, interesting news indeed.
Do you happen to have any measured data for that scrolling improvement?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
I've installed the packages from https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-019/ on my device, and it seems to have
significantly improved scrolling in the browser
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Freiza has been slow since the day I received my device, although I
don't recall what image I first used on it.
It's interesting that there are issues with EGL sync fences - I'm pretty
sure we're using these in Oxide on this device. They're blacklisted on
krillin with the comment "Testing fences
I'm not familiar with Frieza so can't test any of this myself...
If the problem is eglSwapBuffers taking two frames, then that's the same
kind of thing we saw in bug 1563287. Even though we measured the client
(Unity8 itself) was taking two frames, the problem was actually the
server (USC) being
OpenGLES will report a version (containing the string rXpX for a mali
driver). that can be cross checked against malideveloper.com to learn their
age.
On 20 April 2016 at 17:17, kevin gunn wrote:
> Does anyone know the circa of these gpu drivers?
> my assumption is we
Does anyone know the circa of these gpu drivers?
my assumption is we take a snapshot of their android bsp to get them, but do we
know if they are latest and greatest?
we're kinda of at the libhybris/gpu level now - so just thought it's possible
there's driver bug fixes we may benefit from
@dbarth - so did someone run the exact same gl/egl call sequence on android and
prove that the behavior is not exhibited?
i do not see that data here. so we're just making guesses.
@john-mc - i agree a distilled c-app would probably be beneficial
** No longer affects: unity8 (Ubuntu)
--
You
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
Just to make sure it wasn't a one off with the address book app, I did
it again. Here's a few more data points from the log:
qt.scenegraph.time.renderer: time in renderer: total=1ms, preprocess=0,
updates=0, binding=0, rendering=1
qt.scenegraph.time.renderloop: Frame rendered with 'threaded'
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
Oxide only runs on Ubuntu.
But that's still a valid question : if that GPU was to expose such a
slowdown on another OS (Android say), the upstream Blink code would
probably have marked it with a quirk or blacklist to signal the bad
performance of the driver.
So either we end up calling
Until this is a repro written only in C linking the OpenGLES & EGL
libraries (and glibc or bionic), no gpu vendor will take it very
seriously. No-one appears to have addressed my comment in #18 - why does
oxide not see this when it meets this GPU on other OS platforms?
--
You received this bug
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on freiza
Status in
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => 11
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll
loicm kindly pointed me to his qml magnifier demo which should help
expose the FBO performance issue and clarify where the problem is:
https://developer.ubuntu.com/en/blog/2015/04/28/magnifying-glass-qml/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I agree with Chris' assessment. eglSwapBuffers blocking for so long
(over 32ms, i.e. 2 frames at 60Hz) is causing Qt's main loop to block,
compounding the stutter.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
So Oxide (well, chrome proper) has run on this GPU family in both native
(Samsung Chromebook) and Android forms (Nexus 10), and perhaps others.
Does this bug occur there too? Or is it somehow only emergent on our
stack only?
--
You received this bug notification because you are a member of
Marking the Oxide task invalid for now - I've split out Oxide issues in
to new bugs
** Changed in: oxide
Status: Triaged => Invalid
** Changed in: oxide
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
I ran the browser with QSG_RENDER_TIMING=1, and I see timings like this:
qt.scenegraph.time.renderloop: Frame rendered with 'threaded' renderloop in
30ms, sync=0, render=2, swap=28 - (on render thread)
qt.scenegraph.time.renderloop: Frame prepared with 'threaded' renderloop,
polish=0, lock=0,
I pinged the commercial team to ask about a possible driver update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and
I added some more trace events and confirm that the issue shown in the
trace in comment 11 is occurring during this call to
glBindFramebufferEXT, right here:
https://git.launchpad.net/~oxide-
Note, somebody else needs to take a look at this now...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering
I've reported bug 1553302 as well now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on freiza
And a photo of a trace showing the issue in comment 9
** Attachment added: "IMAG0223.jpg"
https://bugs.launchpad.net/oxide/+bug/1550371/+attachment/4588514/+files/IMAG0223.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This is a photo of a trace that shows the issue in comment 8
** Attachment added: "IMAG0222.jpg"
https://bugs.launchpad.net/oxide/+bug/1550371/+attachment/4588513/+files/IMAG0222.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I'm also regularly seeing GLES2DecoderImpl::RestoreFramebufferBindings
block the GPU thread for in excess of 20ms, which is weird. All it's
doing is basically calling glBindFramebufferEXT
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I added a few trace events in Oxide earlier that would aid debugging in
chrome://tracing/. Unfortunately, there's no way to save the trace from
the browser for offline viewing (as it's incompatible with the way we do
downloads) and I can't take a screenshot of it because screenshots on
Freiza are
Missing information in chrome://gpu/ is bug 1552657
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on
So it seems that the required extensions are reported by the driver, but
they're not reported in chrome://gpu/. I'll report another bug for that.
I'm not sure what's going on with the current Oxide version (1.12) - I'm
not doing any debugging on that.
My trunk build of Oxide runs with
I assume any fix here will most likely work on other affected systems
like arale?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow
assigning back as it seems an oxide issue
** Changed in: canonical-devices-system-image
Assignee: Yuan-Chen Cheng (ycheng-twn) => David Barth (dbarth)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in
As pointed out in, we should check why:
EGL_KHR_image, EGL_KHR_image_base and EGL_KHR_gl_texture_2D_image
are not reported by the driver and rule out issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app
** Changed in: canonical-devices-system-image
Assignee: David Barth (dbarth) => Yuan-Chen Cheng (ycheng-twn)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and
** Changed in: oxide
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1550371
Title:
Webbrowser slow scroll and artifact rendering on
Basically, we're falling back to software compositing on Freiza for a
couple of reasons:
- We don't set up a share context on devices where Chromium uses virtual GL
contexts (essentially, all client-side GL contexts are backed by one single GL
context on the GPU service side), as this is
Any updates?
** Changed in: canonical-devices-system-image
Assignee: Pat McGowan (pat-mcgowan) => David Barth (dbarth)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
** Changed in: oxide
Importance: Undecided => Critical
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
46 matches
Mail list logo