Does it happen with an out of the box xmonad ? With no user config?<br><br>On Tuesday, March 6, 2012, Allen S. Rout <<a href="mailto:asr@ufl.edu">asr@ufl.edu</a>> wrote:<br>><br>><br>> A month or so ago, I posted about some slow focus updates I was seeing in xmonad.<br>
><br>> <a href="http://article.gmane.org/gmane.comp.lang.haskell.xmonad/12074">http://article.gmane.org/gmane.comp.lang.haskell.xmonad/12074</a><br>><br>> I noticed another correlation when this is happening, and thought I'd jot it down in this forum, in the hopes that it eventually contributes to a solution.<br>
><br>> During the period when the focus is slowly traversing a lot of intervening windows, I've found that I peg a CPU running the X server; My Xorg process goes to 99%CPU and stays there for the entirety of the delay.<br>
><br>> I've been watching the X cpu behavior because I've also noticed that some Firefox browser behavior will similarly peg the Xorg process for seconds at a time, and I was trying to suss that out.<br>><br>
><br>><br>> I'm kind of free-associating here, but I'm wondering if xmonad's use of X resources is leaving Xorg with a long list of [wumpus] that the X server can't collect or collapse or something, I have no idea what the wumpus might be, but...<br>
><br>> - Allen S. Rout<br>> - Climbing back under his rock<br>><br>><br>> _______________________________________________<br>> xmonad mailing list<br>> <a href="mailto:xmonad@haskell.org">xmonad@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/xmonad">http://www.haskell.org/mailman/listinfo/xmonad</a><br>>