diff options
author | Brian Paul <[email protected]> | 2009-10-22 18:19:01 -0600 |
---|---|---|
committer | Brian Paul <[email protected]> | 2009-10-22 18:20:28 -0600 |
commit | 5e6a6a2719c695996490bde491dac267e52f78af (patch) | |
tree | b9172df37b2299455694fe18118230ff561fa070 | |
parent | 4837e01bcd3d011a38d75cc9f1eff629c3de6fd6 (diff) |
glx: don't destroy context immediately if it's currently bound
According to the GLXDestroyContext() man page, the context should not
immediately be destroyed if it's bound to some thread. Wait until it's
unbound to really delete it. The code for doing the later part is
already present in MakeContextCurrent() so no change was needed there.
-rw-r--r-- | src/glx/x11/glxcmds.c | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/src/glx/x11/glxcmds.c b/src/glx/x11/glxcmds.c index cd4aede74e4..c63116bab77 100644 --- a/src/glx/x11/glxcmds.c +++ b/src/glx/x11/glxcmds.c @@ -540,6 +540,16 @@ DestroyContext(Display * dpy, GLXContext gc) imported = gc->imported; gc->xid = None; + if (gc->currentDpy) { + /* This context is bound to some thread. According to the man page, + * we should not actually delete the context until it's unbound. + * Note that we set gc->xid = None above. In MakeContextCurrent() + * we check for that and delete the context there. + */ + __glXUnlock(); + return; + } + #ifdef GLX_DIRECT_RENDERING /* Destroy the direct rendering context */ if (gc->driContext) { |