Michael Vance wrote:
>
> Another odd thing is that the XSync() is on the flip side of an #ifdef
> Xfree86Server guard--and I'm using the XFree servers for 3Dfx.
So you're using XFree 3.9 with DRI? I haven't examined how the
X/Mesa garbage collection mechanism works in there.
> On Thu, Jan 27, 2000 at 11:17:47AM -0700, Brian Paul wrote:
>
> > Yes, XMesaBufferList should be set to NULL when the last XMesaBuffer
> > is removed from the list.
>
> Hm, free_xmesa_buffer() is never called after the
> glXDestroyContext(). It seems that because I delete my window and
> display after the glXDestroyContext, the garbage collector doesn't get
> rid of it. Then when we try to garbage collect again, the XSync call
> is on a bad display/window, and hangs.
>
> Comments?
Have you looked at glXReleaseBuffersMESA(Display, GLXDrawable)?
If you call this function after destroying your window, Mesa
will free the internal XMesaBuffer associated with the drawable.
However, when using the DRI, this really shouldn't be needed.
Calling the XMesaGarbageCollect() function after the display
has been closed is a problem. I don't know of a way to determine
if a given Display * is valid.
-Brian
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
