[developers] yzlui max cpu

Joshua jcrowgey at uw.edu
Thu Jan 3 01:15:44 CET 2019


Dear DELPH-IN developers:

I'm running lkb and [incr() tsdb] from the logon distribution.  I find
that when I leave a yzlui window open for a while, I starts to gobble up
cpu, running at 100% on one of my cores.  I don't really know how to
help debug further than the following shallow report.

It's repeatedly polling a file and receiving the error message EAGAIN

recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
read(0, 0xffd47770, 10239)              = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
^Crecvmsg(4, strace: Process 24724 detached
 <detached ...>


File 4 is a unix stream socket:

jcrowgey at tsuga:~$ lsof -p 24724 | tail
yzlui   24724 jcrowgey  mem    REG              254,1    37296 14946194 /home/jcrowgey/.cache/fontconfig/8f02d4cb045bd6ce15663e43f347c9f8-le32d4.cache-4
yzlui   24724 jcrowgey  mem    REG              254,1     2072 14946161 /home/jcrowgey/.cache/fontconfig/e0aa53bcfa504e64f87823c16bc01eb6-le32d4.cache-4
yzlui   24724 jcrowgey  mem    REG              254,1    89416 14945737 /home/jcrowgey/.cache/fontconfig/467c019e582ee353435ea5c21d137ef6-le32d4.cache-4
yzlui   24724 jcrowgey  mem    REG              254,1     3960 14945606 /home/jcrowgey/.cache/fontconfig/ca98eee62d98d2fd6bc7905c4b4bb9c4-le32d4.cache-4
yzlui   24724 jcrowgey  mem    REG              254,1   146716 11665409 /lib/i386-linux-gnu/ld-2.24.so
yzlui   24724 jcrowgey    0r  FIFO               0,10      0t0   725500 pipe
yzlui   24724 jcrowgey    1w  FIFO               0,10      0t0   725501 pipe
yzlui   24724 jcrowgey    2w   REG              254,1    36675 11536165 /tmp/yzlui.debug.jcrowgey
yzlui   24724 jcrowgey    3w   REG              254,1    36675 11536165 /tmp/yzlui.debug.jcrowgey
yzlui   24724 jcrowgey    4u  unix 0xffff9edd146d2800      0t0   727375 type=STREAM

I usually just kill the window when this happens and then the cpu cools
down.  My mo for now is just not to keep lui windows open for very long.
It seems like whatever goes wrong doesn't start going wrong until about
3 or 4 minutes have passed.

I'm on i3wm for window manager running on a relatively recent Debian
kernel.  Let me know if you have tips or tricks I might try!

Happy new year!

--
Joshua


----- End forwarded message -----


More information about the developers mailing list