On Tue, Feb 09, 2016 at 02:43:32AM +0000, Stuart Henderson wrote: > I just noticed xstatbar using "quite a lot" more memory than I was > expecting. Does anyone fancy trying to track down the leak? It doesn't > look like any flags are needed to trigger the leak, but using "-s 0" > to avoid sleeping between updates makes it very easy to spot. Cool! I've never tried the -s switch. Setting it to 0 made the cpu graphs match the rhythm to the song currently on my playlist. Poor man's audio visualization!
Cheers, Erling
