If client calls DRI2CreateDrawable multiple times for same drawable
DRI2 creates multiple references. Multiple references cause DRI2 send
multiple invalidate events for same client.
Problem is easy to spot from xtrace. For example following filtered
snippet from problematic client:
000:<:0b85: 16
On Mon, 25 Oct 2010 16:55:35 +0300
Pauli Nieminen wrote:
> If client calls DRI2CreateDrawable multiple times for same drawable
> DRI2 creates multiple references. Multiple references cause DRI2 send
> multiple invalidate events for same client.
I've been burned by the drawable handling code too
From resource management point of view this patch seems correct to me.
Reviewed-by: Rami Ylimäki
On 10/25/2010 04:55 PM, Pauli Nieminen wrote:
If client calls DRI2CreateDrawable multiple times for same drawable
DRI2 creates multiple references. Multiple references cause DRI2 send
multiple inv
On Mon, Oct 25, 2010 at 9:55 AM, Pauli Nieminen
wrote:
> If client calls DRI2CreateDrawable multiple times for same drawable
> DRI2 creates multiple references. Multiple references cause DRI2 send
> multiple invalidate events for same client.
Yup, there is a leak, but I think we should implement