Oxide

Use of share contexts is not correctly disabled when required

Bug #1552376 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
High
Chris Coulson
Oxide branch-1.14
1.13
Fix Released
High
Chris Coulson
Oxide 1.13.5

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.

Chris Coulson (chrisccoulson)
Changed in oxide:
importance: Undecided → High
status: New → Triaged
Chris Coulson (chrisccoulson)
Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
milestone: none → branch-1.14
Chris Coulson (chrisccoulson)
Changed in oxide:
status: Triaged → Fix Released
Revision history for this message
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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.