This appears to be actually working correctly, although what is
displayed in chrome://tracing/ doesn't appear correct
** Changed in: oxide
Importance: High => Undecided
** Changed in: oxide
Status: Triaged => Invalid
** Changed in: oxide
Milestone: branch-1.20 => None
** Changed in: oxide
Assignee: Chris Coulson (chrisccoulson) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1640825
Title:
Investigate why Scheduler::pending_submit_frames is never zero
Status in Oxide:
Invalid
Bug description:
Rendering appears fairly janky on my desktop, so I took a look at
chrome://tracing/ and noticed that Scheduler::pending_submit_frames in
the browser compositor is never zero. I'm pretty sure that this is a
bug (although not necessarily related to my original problem).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1640825/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
