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.
Interesting, couldn't we use XPRESENT instead? Partial present would be possible with that too...
-
-
Almost certainly. I think there are several things wrong with it, such as how it handles multi monitor, etc. The main thing that made me look at it is that it ends up capping rendering to 30fps on my desktophttps://bugzilla.mozilla.org/show_bug.cgi?id=1592786 …
-
Can we replace Firefox's code with my surfman library? ;)
- 1 more reply
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.