On Mon, Jan 13, 2014 at 1:45 PM, Michael Witten
After a while (say, a month) of normal activity, my swap space becomes almost entirely eaten up; the problem can be solved by restarting xmonad (`mod-q').
The problem could well be `xmobar' or `X' itself.
X11 seems unlikely. Memory leaks *are* possible (but unlikely) depending on what you have in your xmonad.hs. (For what it's worth, xmonad isn't even visible on my machine if I sort top by virtual process size. But it's only been running for a couple days thanks to system updates. I don't use xmobar since I run xmonad under xfce.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net