https://bugs.freedesktop.org/show_bug.cgi?id=38312
--- Comment #26 from Benoit Jacob <bja...@mozilla.com> 2011-06-15 08:52:59 PDT --- (In reply to comment #24) > Sorry, I was ambiguous. It's the GL driver's responsibility to defer the > destruction internally. See: > > http://www.opengl.org/sdk/docs/man/xhtml/glXDestroyContext.xml > > I couldn't find a piglit test for this yet. > > That said, it's probably easy to work around this on firefox, until Mesa > handles this correctly. Assuming this is indeed the problem. Oh, that's even more interesting to me. Our code was: glXDestroyContext(mDisplay, mContext); glXDestroyPixmap(mDisplay, mDrawable); We had X errors from MakeCurrent() on closedown suggesting that the X drawable had been destroyed too early. Now it seems that it could just be that since the context was still current, its destruction was postponed, so by the time it actually happened, the drawable has already been destroyed. If that's the case, my latest build should not crash on closedown. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
