ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chrisccoulson@xxxxxxxxxx>]

Public bug reported:

Chrome/Mac uses a browser compositor per RWHV, and seems to have some
logic to recycle compositors when switching tabs. In Oxide, when the
browser switches between tabs, we destroy the compositor and GL context
for the outgoing webview and then create new ones from scratch for the
incoming webview. It would be worth measuring the cost of this,
especially on the phone. It might be worth trying to recycle them in
Oxide too.

** Affects: oxide
     Importance: Medium
         Status: Triaged

** Changed in: oxide
   Importance: Undecided => Medium

** Changed in: oxide
       Status: New => Triaged

-- 
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/1568089

Title:
  Measure webview cost when switching tabs in the browser

Status in Oxide:
  Triaged

Bug description:
  Chrome/Mac uses a browser compositor per RWHV, and seems to have some
  logic to recycle compositors when switching tabs. In Oxide, when the
  browser switches between tabs, we destroy the compositor and GL
  context for the outgoing webview and then create new ones from scratch
  for the incoming webview. It would be worth measuring the cost of
  this, especially on the phone. It might be worth trying to recycle
  them in Oxide too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1568089/+subscriptions