High CPU from gnome-shell with high errors for recvmsg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I am getting high CPU from gnome-shell and I can't track down whats causing the issue.
$ strace: Process 2793 detached
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
38.27 0.047677 1 26640 13464 recvmsg
35.76 0.044550 1 26406 poll
25.77 0.032103 2 13191 writev
0.08 0.000100 2 37 write
0.05 0.000068 0 144 mprotect
0.04 0.000044 0 60 52 stat
0.01 0.000018 0 22 3 futex
0.01 0.000013 0 72 getpid
0.00 0.000006 0 23 read
0.00 0.000003 3 1 sendmsg
0.00 0.000000 0 3 mmap
0.00 0.000000 0 2 munmap
0.00 0.000000 0 86 ioctl
------ ----------- ----------- --------- --------- ----------------
100.00 0.124582 66687 13519 total
$ sudo strace -p 2793 -e trace=recvmsg
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, msg_iov=
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, msg_iov=
recvmsg(19, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(19, {msg_name=NULL, msg_namelen=0, msg_iov=
$ ls -al /proc/2793/fd/19
lrwx------ 1 <removed> <removed> 64 Apr 15 09:07 /proc/2793/fd/19 -> 'socket:[59892]'
lsof |grep 59892
lsof: WARNING: can't stat() nsfs file system /run/docker/
Output information may be incomplete.
lsof: WARNING: can't stat() nsfs file system /run/docker/
Output information may be incomplete.
lsof: WARNING: can't stat() nsfs file system /run/docker/
Output information may be incomplete.
gnome-she 2793 <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2802 gmain <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2805 gdbus <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2806 dconf\x20 <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2808 gnome-s:d <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2809 gnome-s:d <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2810 gnome-s:d <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2811 gnome-s:d <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2813 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2814 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2815 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2816 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2817 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2818 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2819 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 2820 JS\x20Hel <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
gnome-she 2793 5764 threaded- <removed> 19u unix 0x0000000000000000 0t0 59892 type=STREAM
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-
ProcVersionSign
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 08:53:43 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-02-05 (68 days ago)
InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageV
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1880405, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.