On Mon, Jan 13, 2014 at 3:35 PM, Michael Witten wrote:

I'll keep an eye on things; the next time my swap gets suffocated, I'll kill xmobar by itself to see what happens.

Perhaps use `top`, sorting by virtual size. (X will be large, this is something of a lie because `top` cannot tell the difference between actual memory and mapped video memory.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

On Tue, 14 Jan 2014 15:23:57 -0500, Daniel Wagner wrote:

...

On 2014-01-13 13:45, Michael Witten wrote:

Software:

xmonad 0.11 xmobar 0.10 Xorg 1.14.1

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.

Could you include your config file? Perhaps there's something an experienced Haskeller can spot quickly. Then again perhaps not. In any case I have been using xmonad for several years and have not noticed the problem you describe. ~d

~/.xmonad/xmonad.hs ------------------- import XMonad import XMonad.Hooks.DynamicLog main = xmonad =<< xmobar defaultConfig { modMask = mod4Mask, terminal = "urxvtc" } ~/.xmobarrc ----------- Config { font = "xft:DejaVu Sans Mono:size=9" , bgColor = "black" , fgColor = "grey" , position = Top , lowerOnStart = True , commands = [ Run Cpu ["-L","3","-H","50","--normal","green","--high","red"] 10 , Run Memory ["-t","Mem: <usedratio>%"] 10 , Run Swap [] 10 , Run Network "eth2" [] 10 , Run Date "%a %Y-%m-%d %H:%M:%S" "date" 10 , Run StdinReader ] , sepChar = "%" , alignSep = "}{" , template = "%cpu% | %memory% * %swap% | %eth2% } %StdinReader% { %date%</fc>" }

On Wed, 15 Jan, 2014 at 22:03:57 GMT, Michael Witten wrote:

...

...

On 2014-01-13 13:45, Michael Witten wrote: xmobar 0.10

Is there a way to update this? 0.19 is out now.

, Run Swap [] 10 , Run Network "eth2" [] 10

I use the others and have no problems, so it may be these two. I'd really try to get a newer xmobar first though. --Ben

On Sat, 2014-Jan-18, Wirt Wolff wrote:

On Thu, Jan 16, 2014 at 10:18 PM, Ben Boeckel wrote:

...

On Wed, 15 Jan, 2014 at 22:03:57 GMT, Michael Witten wrote:

...

On 2014-01-13 13:45, Michael Witten wrote: xmobar 0.10

Is there a way to update this? 0.19 is out now.

...

, Run Swap [] 10 , Run Network "eth2" [] 10

I use the others and have no problems, so it may be these two. I'd really try to get a newer xmobar first though.

Sorry I came late to the thread. If I read correctly you're using xmobar 0.10 - there's a rather goofy memory leak due to the allocation of colors in xmobar 0.16 and earlier.

So upgrading to a 0.17 or newer xmobar may solve the problem.

xmobar release notes:

http://projects.haskell.org/xmobar/releases.html

Thanks for the heads up! That looks like a promising explanation indeed. I'll upgrade presently, and then let the list know how it goes in a month or so. I thank everybody for taking the time to provide input.