display, I'll wait on that.
thanks
andy
-Original Message-
From: Brian Paul [mailto:bri...@vmware.com]
Sent: Friday, May 03, 2013 1:04 PM
To: Andy Skinner
Cc: mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] visual leak?
On 05/03/2013 09:42 AM, Andy Skinner wrote:
> Hi, Bri
like a leak to me, even
in current Mesa.
thanks
andy
-Original Message-----
From: Andy Skinner
Sent: Monday, April 29, 2013 1:04 PM
To: 'Brian Paul'
Cc: mesa-dev@lists.freedesktop.org
Subject: RE: [Mesa-dev] visual leak?
Thanks. I realized today that newer Mesa registers the di
thanks
andy
-Original Message-
From: Brian Paul [mailto:bri...@vmware.com]
Sent: Monday, April 29, 2013 11:39 AM
To: Andy Skinner
Cc: mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] visual leak?
On 04/26/2013 03:23 PM, Andy Skinner wrote:
> Hi. We are seeing a leak of things created in X
Hi. We are seeing a leak of things created in XMesaCreateVisual, as called
from fakeglx.c. I don't see anywhere that XMesaDestroyVisual is called. I see
a free() in destroy_visuals_on_display, but I don't know how often that is
called. Are these visuals intended to be kept around?
The visua
I want to submit our patch and see what people thought. See the previous email
with the same subject as above (with PATCH flag).
This change is intended to reduce the chances of XSync being called for a
Display* on any old thread. The garbage collection looks at every buffer, and
when a Displ
Hi. We've had some problems with XMesaGarbageCollect with multiple threads.
For various reasons, we've had different Display pointers on different threads.
We have a problem when XSync is called on a Display in the list of Mesa
buffers, on a thread where we weren't intending to handle that Di
