diff options
| author | Sven Gothel <[email protected]> | 2011-08-30 03:50:31 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2011-08-30 03:50:31 +0200 |
| commit | 9ed513e9a9616f6028084df4c650c8caf31ea49d (patch) | |
| tree | 5e8ea1af38a83d2e29b0762461e594153c133953 /src/newt/native/NewtCommon.c | |
| parent | 9c64f265f4e3aaef85b7f017493e3695f46e00b3 (diff) | |
Workaround (Fix) for Bug 502: Multithreading issue w/ libX11 1.4.2 and libxcb 1.7 bug 20708
See https://jogamp.org/bugzilla/show_bug.cgi?id=502
Since the libX11/xcb code doesn't seem to be fixed anytime soon
a better usable workaround is required than using a system property
to enable 'over locking'.
It turns out that the race condition is related to the parallel
X11 Display connection usage of GLX/OpenGL and event dispatching.
This workaround utilizes 2 X11 Display handles, one for windowing/OpenGL
and one for event dispatching.
This approach allows us to cont. multithreading use w/o locking the display
and works on both implementations, the old bug-free libX11 and the 'new' buggy one.
Downside is the little resource overhead of the 2nd X11 Display connection .. well.
- Removes the property: 'nativewindow.x11.mt-bug'
Diffstat (limited to 'src/newt/native/NewtCommon.c')
0 files changed, 0 insertions, 0 deletions