i wanted to ask what is the reason for the slow updates when resizing windows. the slowness is one of the main points that keeps me from using compiz as my regular window manager. thanks in advance
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
There's something strange about resizing with the mouse that goes beyond slowness. I experience the following with Acrobat Reader, Firefox and Thunderbird: (1) Open a window, filling less than full screen. (2) Left-click the right-hand border to begin a drag. (3) Drag the right-hand border to the right; do not release the mouse. (4) Wait, while still holding the left mouse button down, but not moving it. Expected result: The window is eventually redrawn with its right-hand border at the position of the mouse. Actual result: The mousse cursor may be three inches past the edge of the window, but the window never resizes. The window will not resize until the mouse twitches again (i.e. move the mouse a little more). It seems that a redraw is triggered only by a mouse movement: as long as the mouse is stationary during the drag, the window will not be redrawn, even if the mouse position is well outside the window.
Resizing a redirected window on composited desktop is much more expensive than resizing a window on a regular desktop. Mainly because you have to allocate a new buffer for the window, copy the old contents to this new buffer and wait for the application to redraw missing parts. On a regular desktop you just change the clipping region for the window and have the application redraw missing parts. The strange resizing issue you noticed should now be fixed. Thanks for reporting that one.
Anyone working on this?
big thanks to everyone working on compiz and the free ati drivers. the problem is solved for me now with a regular ubuntu gutsy install.
It is? I figured Gutsy was using the resize mode it does just because this preformance problem was still around.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.