#536386 conky: uses all my spare CPU cycles unless rebuilt with --disable-xdamage

Package:
conky
Source:
conky
Submitter:
Ryan Niebur
Date:
2014-09-02 06:15:05 UTC
Severity:
normal
#536386#5
Date:
2009-07-09 15:26:00 UTC
From:
To:
When I was going to adopt it I was going to add --disable-xdamage to
the configure options in the package (if I determined it wouldn't have
any bad side affects, of course). I am not the only person able to
reproduce this, I originally learned this solution from some bug
report (somewhere..). Right now I use a locally rebuilt package.
Please consider adding this flag to configure, or fixing the bug, of
course :). I will provide more information if needed, just ask.
#536386#10
Date:
2009-07-10 00:24:23 UTC
From:
To:
Hello,

Are you using the default .conkyrc file?

One reason that memory utilisation is high is if double_buffer is
used without own_window

Regards,

Kapil.
--
#536386#15
Date:
2009-07-11 09:26:40 UTC
From:
To:
gah, your email ended up in my spam box.

no, when I first got the problem I was using the one from here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486649#10

I am now using double_buffer with own_window without problems with my
rebuilt package.

it's clearly related to the xdamage stuff, because I am a very happy
conky user with a 0.00 load average now that I've recompiled. :)

Cheers,
Ryan
#536386#24
Date:
2010-03-01 17:53:22 UTC
From:
To:
Ryan,

what is your window manager?
This is very likely due to the fact that it is trying to resize conky.
You can simply solve it by using 'alignment none'.

C.
#536386#33
Date:
2014-06-02 20:42:57 UTC
From:
To:
PLEASE CAN I SEE YOUR ATTENTION FOR A BRIEF DISCUSS.
#536386#38
Date:
2014-09-02 06:12:45 UTC
From:
To:
Hello,

I'm able to reproduce this problem with stock configurations of dwm and
conky in wheezy.
Also happens with spectrwm-2.6.0.

How to reproduce:
1) start a dwm X session: startx /us/bin/dwm
2) start conky
3) start some other X client (e.g. xterm) - only needed if conky isn't
floating

when the other client is focused and conky looses focues, the bug is
triggered. Refocusing conky won't help.
If conky is started in floating mode, the bug is triggered immediately.
These trigger scenarios works the same way in spectrwm.
Debugging with GDB shows that indeed it is the Xdamage extensions emitting
too many events.

However, I wasn't able to reproduce this with the twm floating window
manager. As this bug isn't common, it is quite likely that most floating
window managers aren't affected.
Yet the tilling window managers I tested trigger the bug in floating mode.
All in all it seems rhis has something to do with how the WM treats conky.

Kind regards,
Ondřej Grover