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.
-
-
Thankfully I've never used anything that touches Wayland or swrast... I'd be curious if not racing the init fixes it, but this sounds more like an upstream bug than a bug with GLX.
-
Also - as a note - I don't believe I've ever marshaled things between threads with GLX, they've always been independent, so it is possible that there could still be issues what your specific use case.
End of conversation
New conversation -
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.