On Thu, 2009-04-16 at 04:24 +0100, Dave Airlie wrote: > valgrind was showing a race between the drawable getting destroyed > by the X resource freeing code, and the context getting destroyed > later and freeing the drawable.
Does that still happen with Kristian's GLX drawable private leak fix? > However I've no idea if some other combination of things could cause > this code to leak. Though indeed I've been wondering if Kristian's fix couldn't cause problems of its own due to just NULLing out the context drawable pointers in DrawableGone() but not doing the flushing etc. done in DoMakeCurrent(). -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
