Consider aborting the process after GL_OUT_OF_MEMORY
lcnr opened this issue · 0 comments
lcnr commented
According to the official reference, OpenGL is in an undefined state after aborting.
As I don't want to deal with any of this it might be a good idea to abort the process once this happens.
Other alternatives:
- just
panic!instead (what is currently done) - return something like
ErrKind::FatalOutOfMemory
We could poison the Backend once OpenGL is oom, even if I currently don't want to do it (small performance + maintanance cost)