[cairo] Solid surface cache causing cross-thread unhappiness

[Bill Spitzak]

Don't use the xlib locking, it is really slow! And it just serializes 
each call, it would not fix where thread 1 tries to do two things to a 
surface with two xlib calls, and thread 2 sticks a delete-this-surface 
inbetween them.

On Feb 28, 2007, at 6:38 PM, Carl Worth wrote:

> 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.