Comment 226 for bug 182038

An update on my lack of progress.

One possible source of error is XPutImage.
An XPutImage is an XPutImage Request followed by the pixel data. If some X call is being made on an signal handler or a different thread, this could disrupt
this call. XPutImage alloc's an xrequest, then analyzes the data, which may
do more work because the image doesn't fit in the box specified, and then sends
the data. I think there's a window between the xrequest alloc and the data
sent in which such a scenario might happen.

I started tracking down what calls XPutImage, and found that the adobe flash
plugin was being called one or more times a second, and winds up calling
XPutImage. (why?)

A more efficient method of transferring image data to the server is through
an X shared memory protocol. I'll have to see if this is being used.