<div dir="ltr">Why would xeyes generate a large number of rectangles in a composited environment? Are you talking about the initial expose? </div><div class="gmail_extra"> <div class="gmail_quote">On Thu, Sep 18, 2014 at 4:49 PM, Keith Packard <<a href="mailto:keithp@keithp.com" target="_blank">keithp@keithp.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adam Jackson <<a href="mailto:ajax@redhat.com">ajax@redhat.com</a>> writes: > In attempting to get the Always mode of backing store working again, I > felt the urge to clean the place up a bit. The most notable change here > is removing the (questionable) optimization from exposure event generation > to emit a bounding-box event when faced with more than 25 rects in the > exposed region. Given that toolkits already coalesce consecutive expose > boxes, and that you'll never hit it in a composited environment anyway, > the complexity doesn't seem justified. This was written to address shaped windows, which can still generate a large number of rectangles, even in a composited environment. I think xeyes was the original test case; a full-screen xeyes window has a couple thousand rectangles, or about 64kB of data. I suspect an xeyes-specific optimization is not all that useful to keep around, but I fear that some user somewhere is taking advantage of this... -- <a href="mailto:keith.packard@intel.com">keith.packard@intel.com</a> _______________________________________________ <a href="mailto:xorg-devel@lists.x.org">xorg-devel@lists.x.org</a>: X.Org development Archives: <a href="http://lists.x.org/archives/xorg-devel" target="_blank">http://lists.x.org/archives/xorg-devel</a> Info: <a href="http://lists.x.org/mailman/listinfo/xorg-devel" target="_blank">http://lists.x.org/mailman/listinfo/xorg-devel</a> </blockquote></div> -- Jasper </div>