Resizing and scrolling very slow when running a compositing manager

[Xavier Bestel]

On Thu, 2006-05-11 at 15:34, Brian Paul wrote:

> > Just allocating once the maximum size (i.e. the size when the mouse
> > cursor is at the bottom-right corner of the screen) seems a much better
> > strategy.
> 
> I think that would work, but it also seems excessive.

Well, the memory needed must be available because otherwise you just
can't resize the window, and this memory shouldn't be needed by anthing
else. In fact you can see that as reserving potentially needed memory
for the current resize operation.
And as the number of reallocations drastically falls (1 at start, 1
after finishing), you could even say it's way less excessive than the
other proposed method :)

	Xav