Comment 10 for bug 1496525

It also might just be _Unity itself_, and increasingly it does seem like Unity was written in a way that requires it to poll the entire desktop(?) on a more frequent basis than the compositor would be doing on its own, specifically in order to handle issues arising from xrandr (monitor hotplugging) and other edge cases.

So far the three ways I've managed to crash the session after this "optimization"/breakage are:
- Hotplugging a display
- Super+D to show all windows again after hiding them
- Skype doing something weird when someone got added to a call (who the heck knows what Skype thinks it's doing with Xorg anyway)

So if these could be handled somehow without whatever it is that Unity is doing normally to bottleneck ... I can't emphasize enough that it really reverses my Unity/compiz stereotypes.