Re: Borders and unmap with Composite

Around 18 o'clock on Nov 13, Brian Paul wrote:

> This reminds me of a GL issue.  Suppose you have two rendering contexts
> sharing a texture.  If the first context calls glDeleteTexture while the
> second context is still using the texture we've got a potential problem.
> The usual solution is reference counting.  Binding (using) the texture
> increments the counter. Unbinding or deleting decrements the counter.  When
> the counter hits zero, we can really delete the texture.

Yes, it's precisely the same issue.  Implicit in the compositing-manager
provided name (Pixmap ID) for the pixmap is a reference which will be
decremented when the compositing manager destroys the name.  That's why it 
will fix the problem; the pixmap won't go away until its reference count 
hits zero.

-keith