Measure webview cost when switching tabs in the browser
Bug #1568089 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Triaged
|
Medium
|
Unassigned | ||
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.
| Changed in oxide: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #1 |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #2 |
Revision history for this message
| Chris Coulson (chrisccoulson) wrote | #3 |
To post a comment you must log in.
Note that in webbrowser-app, when switching from one tab(webview) to another one, we currently delay hiding the current tab until after the new tab has been shown, to work around bug #1502675. That means that we can have two visible webviews for a fraction of a second.