Under certain conditions, updating textures results in a context lost event. If a texture load happens during or immediately after this event, the texture will fail to load with
Unable to create texture but the error handler on that texture never fires.
If you then check the
engine._gl.isContextLost() status, it will sometimes be true or sometimes be false.
What I think is happening is that Babylon is recovering from the loss of context but does not attempt to reclaim any pending texture loads. You can see the issue demonstrated here:
My question is, should Babylon keep track of operations that failed because the context was lost, and on recovery attempt to continue the previous track?