Public bug reported:
GL share groups are unreliable on some GPU drivers, and Chromium works
around these by using "virtualized" GL contexts (essentially, client-
side contexts within a client-side share group are backed by a single
service-side GL context). However, Oxide depends on share groups for
hardware compositing which means we don't benefit from the Chromium
workaround.
To avoid this, we should have a texture-backed EGLImage compositing path
to avoid the share group dependency
** Affects: oxide
Importance: Critical
Assignee: Chris Coulson (chrisccoulson)
Status: In Progress
** Changed in: oxide
Importance: Undecided => Critical
** Changed in: oxide
Status: New => In Progress
** Changed in: oxide
Milestone: None => branch-1.7
** Changed in: oxide
Assignee: (unassigned) => Chris Coulson (chrisccoulson)
--
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/1435831
Title:
Support compositing path using EGLImage
Status in Oxide Webview:
In Progress
Bug description:
GL share groups are unreliable on some GPU drivers, and Chromium works
around these by using "virtualized" GL contexts (essentially, client-
side contexts within a client-side share group are backed by a single
service-side GL context). However, Oxide depends on share groups for
hardware compositing which means we don't benefit from the Chromium
workaround.
To avoid this, we should have a texture-backed EGLImage compositing
path to avoid the share group dependency
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1435831/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
