You are not logged in.

#1 2016-10-09 11:38:14

ohnonot
...again
Registered: 2015-09-29
Posts: 5,592

dwm: conky eats 100%CPU when it has its own window

there it is in the title.
this only happens with dwm, not with openbox (same config files).

short version

i tested this with a bare minmal conky, and the behaviour is consistent:

own_window yes
own_window_type normal # or dock, desktop. NOT with override

TEXT
bla

as soon as the conky gets its own window, the cpu goes to 100%.
as soon as it shows on the root window, cpu is unaffected.

=======================================================

long explanation

i have 3 conkys - 1 is constantly on the desktop/rootwindow with

own_window yes
own_window_transparent yes
own_window_type override
own_window_title Conky

and causes NO problems.

the other 2 have

own_window yes
own_window_transparent no
own_window_type normal
own_window_argb_visual no

and i open them through a keybind.

when i do, the cpu goes to 100% immediately, fan spinning like crazy.

"sudo top -o '%CPU'" has this to say:

top - 14:10:04 up  2:09,  1 user,  load average: 0.66, 0.32, 0.22
Tasks: 144 total,   2 running, 142 sleeping,   0 stopped,   0 zombie
%Cpu0  :  12.2/31.1   43[|||||||||||||||||||||||||||||||||                                            ]
%Cpu1  :   0.0/0.7     1[|                                                                            ]
%Cpu2  :   4.9/28.7   34[||||||||||||||||||||||||||                                                   ]
%Cpu3  :  20.9/59.7   81[||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||               ]
GiB Mem : 11.7/6.773    [                                                                             ]
GiB Swap:  0.0/4.000    [                                                                             ]

  PID USER      PR  NI    VIRT    RES  %CPU %MEM     TIME+ S COMMAND                                   
15562 user      20   0  271.0m  51.1m  94.0  0.7   5:36.04 R Xorg                                      
25650 user      20   0  109.1m  13.8m  71.3  0.2   0:17.43 S conky                                     
    1 root      20   0   51.9m   6.2m   0.0  0.1   0:01.19 S systemd                                   

this is the same however i change other settings in the conkys; i can even replace the whole 'TEXT' section with a single 'bla'.

i also tried

#own_window_type normal
own_window_hints sticky,skip_taskbar,skip_pager,above

and a few other options, to no avail.

Conky 1.9.0 compiled Sun Oct  9 14:47:53 EEST 2016 for Linux 4.7.6-1-ARCH (x86_64)
xorg-server 1.18.4-1

Last edited by ohnonot (2016-10-09 11:50:00)

Offline

#2 2016-10-09 12:46:04

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: dwm: conky eats 100%CPU when it has its own window

I can replicate this on Alpine with conky 1.10:
2016-10-09-131846_1280x800_scrot.th.png

~ > conky --version
conky 1.10.3_pre compiled Thu Jun 30 12:18:40 GMT 2016 for Linux 4.1.20-0-grsec x86_64

Interestingly, xorg just ticks over normally with this system.

xorg-server-1.18.4-r1

EDIT: No, it doesn't, I forgot that I can't view root processes as a normal user under a grsec kernel :8

`sudo htop` shows that xorg is also eating lots of cycles.

EDIT2: a quick `strace` showed thousands of these lines:

select(4, [3], NULL, NULL, {0, 0})      = 0 (Timeout)
poll([{fd=4, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=4, revents=POLLOUT}])
writev(4, [{iov_base="\216\3\4\0\4\0\240\0\5\0\240\0\0\0\0\0\211\v\2\0\5\0\240\0", iov_len=24}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 24
recvmsg(4, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="Z\3J\317\1\0\240\0\4\0\240\0\370\312\267\0\0\0\0\0}\1\f\3\1\0\23\0}\1\f\3", iov_len=4096}], msg_iovlen=1, msg_controllen
=0, msg_flags=0}, 0) = 32
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)

Perhaps an upstream bug report is called for here?

Last edited by Head_on_a_Stick (2016-10-09 13:06:02)

Offline

#3 2016-10-09 20:23:53

ohnonot
...again
Registered: 2015-09-29
Posts: 5,592

Re: dwm: conky eats 100%CPU when it has its own window

hmm.
i had half hoped it was a conky 1.9. problem.
oh well...

Head_on_a_Stick wrote:

a quick `strace` showed thousands of these lines:

select(4, [3], NULL, NULL, {0, 0})      = 0 (Timeout)
poll([{fd=4, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=4, revents=POLLOUT}])
writev(4, [{iov_base="\216\3\4\0\4\0\240\0\5\0\240\0\0\0\0\0\211\v\2\0\5\0\240\0", iov_len=24}, {iov_base=NULL, iov_len=0}, {iov_base="", iov_len=0}], 3) = 24
recvmsg(4, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="Z\3J\317\1\0\240\0\4\0\240\0\370\312\267\0\0\0\0\0}\1\f\3\1\0\23\0}\1\f\3", iov_len=4096}], msg_iovlen=1, msg_controllen
=0, msg_flags=0}, 0) = 32
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)

this is just cryptic.
any idea if it could have something to do with the window manager?
maybe i should try with other tiling managers...

Perhaps an upstream bug report is called for here?

yes...
sourceforge or github?

Offline

#4 2016-10-10 06:20:42

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: dwm: conky eats 100%CPU when it has its own window

ohnonot wrote:

Perhaps an upstream bug report is called for here?

yes...
sourceforge or github?

Ah yes, the github page is the one I should have linked -- that is given as the source on the Arch package page.

https://www.archlinux.org/packages/extra/x86_64/conky/

Offline

Board footer

Powered by FluxBB