The destructor for TextureRefHolder does not handle a lost context

Bug #1427882 reported by Chris Coulson on 2015-03-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Undecided
Chris Coulson

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

Changed in oxide:
assignee: nobody → Chris Coulson (chrisccoulson)
status: New → Fix Released
milestone: none → branch-1.6
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers