Issue 213 in xmonad: UrgencyHook fails under stress-testing

Comment #2 on issue 213 by wirtwolff: UrgencyHook fails under stress-testing http://code.google.com/p/xmonad/issues/detail?id=213 Yes, indeed, xmonad remains responsive with stable memory usage here, both with and without urgencyHooks. I wouldn't recommend using a dzenUrgencyHook with this test, though. ;-) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Devin, anyone else, have further comments? Should this issue be closed? I did notice a very very slow increase in memory usage by whatever terminal runs the script, but nothing in xmonad, even after leaving this running for a half hour wasting cpu cycles. -- wmw
participants (2)
-
codesite-noreply@google.com
-
Wirt Wolff