From 7b09a9428203db5c0c46b9226ba1d5a06f17b2d8 Mon Sep 17 00:00:00 2001 From: Mathias Froehlich Date: Thu, 13 Oct 2011 11:32:35 +0200 Subject: st/wgl: Release stw_framebuffer::mutex after pbuffer creation. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This change releases the stw_framebuffer::mutex past creation of the pbuffer stw_framebuffer. Without this change the pbuffers lock is never released. Since on win32 mutexes are recursive, this does not hurt as long as all actions on a context are done from the same thread. But if, for example, context creation happens in a different thread than usage, every access to the context will block for ever. Signed-off-by: José Fonseca --- src/gallium/state_trackers/wgl/stw_ext_pbuffer.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/gallium/state_trackers/wgl/stw_ext_pbuffer.c b/src/gallium/state_trackers/wgl/stw_ext_pbuffer.c index c7273f26545..252d07a90cc 100644 --- a/src/gallium/state_trackers/wgl/stw_ext_pbuffer.c +++ b/src/gallium/state_trackers/wgl/stw_ext_pbuffer.c @@ -209,6 +209,8 @@ wglCreatePbufferARB(HDC _hDC, fb = stw_framebuffer_create(hDC, iPixelFormat); if (!fb) { SetLastError(ERROR_NO_SYSTEM_RESOURCES); + } else { + stw_framebuffer_release(fb); } return (HPBUFFERARB)fb; -- cgit v1.2.3