PSA: GLX is not thread safe, even if you use XLockDisplay()/XUnlockDisplay(). Xlib-XCB does not fix this. First Google result on this is a wrong Stack Overflow answer. GLX uses lots of per-process (not per-display) globals. You must use a process-wide lock around each GLX call.
Of course if you aren't using OpenGL there is no need for GLX :) But we have to support WebGL.
-
-
I am using openGL, but not on macos. I have metal/osx, dx11/win32, webGL/wasm, openGL/linux now as supported backends. Alright so we'll be good with EGL then. Thanks :)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.