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.
-
-
They are two completely different contexts, as though it was two entirely different processes. The GPU drivers handle the scheduling. I've been doing this for a while and have never seen an issue.
-
No, that’s not true. Your first GLX call from multiple threads will call __glxInitialize unsynchronized and randomly crash. Check out https://github.com/pcwalton/surfman/commit/b8de64d30b7cd21c74545a98c3af6e30864c776e … and “cd surfman/surfman && cargo test”. Observe random failures.
- 5 more replies
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.