ubuntu-webapps-bugs team mailing list archive

[Chris Coulson <chris.coulson@xxxxxxxxxxxxx>]

Public bug reported:

The destructor for TextureRefHolder calls GLES2Decoder::MakeCurrent()
before dropping its reference to TextureRef, but MakeCurrent() will fail
if the GL context is lost. In this case, bad things will happen if
TextureRef is the last reference to the underlying Texture, as
TextureManager assumes the caller has made the context current and
attempts to delete the texture

** Affects: oxide
     Importance: Undecided
     Assignee: Chris Coulson (chrisccoulson)
         Status: Fix Released

** Changed in: oxide
     Assignee: (unassigned) => Chris Coulson (chrisccoulson)

** Changed in: oxide
       Status: New => Fix Released

** Changed in: oxide
    Milestone: None => branch-1.6

-- 
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/1427882

Title:
  The destructor for TextureRefHolder does not handle a lost context

Status in Oxide Webview:
  Fix Released

Bug description:
  The destructor for TextureRefHolder calls GLES2Decoder::MakeCurrent()
  before dropping its reference to TextureRef, but MakeCurrent() will
  fail if the GL context is lost. In this case, bad things will happen
  if TextureRef is the last reference to the underlying Texture, as
  TextureManager assumes the caller has made the context current and
  attempts to delete the texture

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