Hi! On Sat, 2013-08-31 at 15:27:32 +0200, Julien Danjou wrote: > On Sat, Aug 31 2013, Guillem Jover wrote: > > Since I upgraded to 3.5.x around two months ago, I've started to sense > > the system becoming very sluggish. The other day checking ps output I > > found that awesome was taking 800 MiB of resident memory. After > > restarting it, the process went back to the normal 12 MiB or so. > > > > I've noticed that the memory increases (at least) every time I switch > > window, either with the keyboard (f.ex. Mod4 + l, Mod4 + k) or with > > the mouse. If I keep, say, Mod4 + l pressed permanently I can easily > > get the awesome process to increase around 1 MiB every 5 seconds. > > > > I've set the severity to serious because this is a long-lived process, > > and the effects of a leak affect the whole system, but of course if > > you disagree please lower it. > > The severity sounds right, however that can be triggered by Lua code; > are you running with the default configuration ?
Yeah, I already considered that and disabled the code I thought could have introduced leaks (a custom battery widget), but that did not seem to help. Just to make extra sure now, I've moved ~/.config/awesome aside, restarted awesome and it still shows the same behavior. For me it's very easy to reproduce, on a empty tag, open two xterms, and on one of the xterms start top (sorting processes by memory ‘M’), and then hold Mod4 + l down for a while and see the x-window-manager process increase memory usage. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
