ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

A change in Chromium recently causes GpuDataManager to be initialized
later, after we use it in BrowserMainParts::PreCreateThreads to check if
virtual GL contexts are enabled. This causes us to always use a share
context when one is provided, even when we shouldn't.

** Affects: oxide
     Importance: High
         Status: Triaged

** Affects: oxide/1.13
     Importance: High
         Status: Triaged

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

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

** Also affects: oxide/1.13
   Importance: Undecided
       Status: New

** Changed in: oxide/1.13
   Importance: Undecided => High

** Changed in: oxide/1.13
       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/1552376

Title:
  Use of share contexts is not correctly disabled when required

Status in Oxide:
  Triaged
Status in Oxide 1.13 series:
  Triaged

Bug description:
  A change in Chromium recently causes GpuDataManager to be initialized
  later, after we use it in BrowserMainParts::PreCreateThreads to check
  if virtual GL contexts are enabled. This causes us to always use a
  share context when one is provided, even when we shouldn't.

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