Use of share contexts is not correctly disabled when required

Bug #1552376 reported by Chris Coulson on 2016-03-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
High
Chris Coulson
1.13
High
Chris Coulson

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.

Changed in oxide:
importance: Undecided → High
status: New → Triaged
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.14
Changed in oxide:
status: Triaged → Fix Released
Pat McGowan (pat-mcgowan) wrote :

@chris is this related to bug #1550371?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers