Open m-7761 opened 5 years ago
Maybe it's not ~TextureWidget. It calls makeCurrent:
if(isValid())
{
makeCurrent();
glDeleteTextures(1,&m_glTexture);
// Do NOT free m_texture. TextureManager does that.
glDeleteTextures(2,m_scrollTextures);
}
Or maybe this bug is fixed but not in the current release.
No fix was committed for this since last release (Maverick 1.3.11).
I'm curious to know what the problem is. I don't think it will affect my rewritten code. But I can't see where it's coming from either.
~TextureWidget needs to select the appropriate OpenGL context before it deletes its textures.
EDITED: I actually don't think this is an accurate description since ~TextureWidget seems to set the context. See follow-up post.