Compiz "normal" resize laggy on snapped windows

[Egmont Koblinger]

In ccsm select Enable Snapping Windows (screen edges or window edges or both), and in the Resize plugin's settings choose Default Resize Mode: Normal.

Take a window whose left edge is snapped (either to the left of the screen, or to the right edge of another window; in accordance with to the settings of the Snapping plugin), and try to resize it at the right edge (or whichever right corner).

If you resize by simply dragging with the mouse, or by Alt+F8, you'll see that the window is only refreshed when the first few pixel move is made by the mouse, then it freezes. Even after releasing the mouse, it takes long seconds until the window is properly refreshed and the mouse grab is released. The same happens if you resize by Alt+middleclick whereas the mouse is initially near the right edge of the window.

If you resize by Alt+middleclick, and the mouse is further away from the right edge (towards the middle of the window), you'll see that the window is continuously redrawn, but its right edge (and hence its width) keeps jumping back and forth by ~50 pixels or so.

The same happens at the opposite edge, i.e. when the window's right edge is snapped, and you try to resize by the left edge.

The bug occurs with all applications I've tried, including e.g. firefox, ccsm, geeqie, and gnome-terminal (which has a size constraint).

The bug does not happen at the top or bottom edges. The bug does not happen if the window's corresponding edge happens to align as if the window was snapped but actually the snap feature is disabled. The bug does not happen if snapping is enabled but the opposite edge is not at a snapped location. The bug does not happen with other resize modes (outline, rectangle etc.).

Ubuntu 12.10 Quantal Quetzal, Unity desktop.

[Daniel van Vugt (vanvugt)]

Confirmed. I thought I had logged this bug already but can't find it.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1019139, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.