[cairo] Solid surface cache causing cross-thread unhappiness

Behdad Esfahbod behdad at behdad.org
Wed Feb 28 11:39:34 PST 2007

On Wed, 2007-02-28 at 10:38 -0800, Carl Worth wrote:
> It's probably just causing to threads to call into the same Display*
> and making Xlib all over.
> Now, I think there's some locking that the application can turn on for
> Xlib (or through GDK) that could make this work. But a question is
> whether it's reasonable for a user to expect that using cairo's image
> backend in one thread could call into the Display* of xlib surfaces
> used only in separate threads. 

I see.  This leaves no chance other than pushing the caching into
backends, and xlib should do per-display caching.  I'm going to revert
the patch for 1.4 while we think about how to fix it.


"Those who would give up Essential Liberty to purchase a little
 Temporary Safety, deserve neither Liberty nor Safety."
        -- Benjamin Franklin, 1759

More information about the cairo mailing list