Matan Addam

@ItsVeeBot what this means is that your code should manage the active OpenGL context that your process holds to when it is drawing or preparing elements for drawing through pyglet...

Maybe some API for identifying the OpenGL context (?!) could be one way for developers to scaffold this safety around their code flows rather than relying purely on theoretical analyses...

As a side effect of deleneating it in the above I think I have a clearer picture of how to think about my code such that I know exactly where...

Thanks a lot for suggesting `pyglet.gl.current_context` as an affordance in this area, I can then log the object address during development mode just to assure that I have the right...

(It's probably time to remove the 'bug' label).

Thanks. This was indeed apparently resolved by more carefully managing the window resizing api and process. It has not reproduced on any machine ever since that time. Thanks again.