I did perf record and report and here is the output I got. I closed everything.
54.48% 0.00% gnome-shell [unknown] [.] 0000000000000000 + 24.73% 0.21% gnome-shell [kernel.kallsyms] [k] entry_SYSCALL_64_after_hwframe + 24.35% 0.12% gnome-shell [kernel.kallsyms] [k] do_syscall_64 + 23.20% 0.29% gnome-shell [kernel.kallsyms] [k] x64_sys_call + 18.53% 9.64% gnome-shell libgraphene-1.0.so.0.1000.8 [.] graphene_matrix_multiply + 17.08% 0.00% gnome-shell [unknown] [k] 0x0000000100000008 + 16.89% 0.15% gnome-shell libc.so.6 [.] __poll + 15.72% 0.11% gnome-shell [kernel.kallsyms] [k] __x64_sys_poll + 15.53% 0.14% gnome-shell [kernel.kallsyms] [k] do_sys_poll + 12.31% 1.44% gnome-shell [kernel.kallsyms] [k] do_poll.constprop.0 + 9.71% 0.00% gnome-shell [unknown] [.] 0x0000000200000004 + 9.65% 0.00% gnome-shell [unknown] [.] 0x0000000200000002 + 9.39% 0.00% gnome-shell [unknown] [.] 0x0000000200000003 + 4.69% 1.96% gnome-shell [kernel.kallsyms] [k] timerfd_poll + 3.96% 3.21% gnome-shell libglib-2.0.so.0.7200.4 [.] g_main_context_check + 3.28% 0.00% gnome-shell [unknown] [.] 0x000055633190de50 + 3.15% 0.13% gnome-shell libc.so.6 [.] __libc_recvmsg + 3.00% 0.00% gnome-shell [unknown] [.] 0x0000000000000001 + 2.81% 0.54% gnome-shell [kernel.kallsyms] [k] _raw_spin_lock_irqsave + 2.75% 0.00% gnome-shell libc.so.6 [.] __libc_sendmsg + 2.71% 0.53% gnome-shell [kernel.kallsyms] [k] __raw_spin_lock_irqsave + 2.67% 0.98% gnome-shell libgraphene-1.0.so.0.1000.8 [.] graphene_vec4_dot + 2.63% 0.02% gnome-shell [kernel.kallsyms] [k] __x64_sys_sendmsg + 2.61% 0.10% gnome-shell [kernel.kallsyms] [k] __x64_sys_recvmsg + 2.60% 0.06% gnome-shell [kernel.kallsyms] [k] __sys_sendmsg + 2.56% 0.01% gnome-shell [kernel.kallsyms] [k] schedule_hrtimeout_range + 2.54% 0.11% gnome-shell [kernel.kallsyms] [k] __sys_recvmsg + 2.53% 0.05% gnome-shell [kernel.kallsyms] [k] schedule_hrtimeout_range_clock + 2.52% 0.90% gnome-shell [kernel.kallsyms] [k] __fget_light + 2.52% 0.07% gnome-shell [kernel.kallsyms] [k] ___sys_sendmsg + 2.39% 0.40% gnome-shell [kernel.kallsyms] [k] __fdget + 2.37% 0.07% gnome-shell [kernel.kallsyms] [k] ____sys_sendmsg + 2.34% 0.02% gnome-shell [kernel.kallsyms] [k] schedule + 2.30% 0.07% gnome-shell [kernel.kallsyms] [k] __schedule + 2.29% 2.21% gnome-shell libc.so.6 [.] __memmove_avx512_unaligned_erms + 2.20% 0.05% gnome-shell [kernel.kallsyms] [k] unix_stream_sendmsg + 2.17% 0.10% gnome-shell [kernel.kallsyms] [k] ___sys_recvmsg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2079042 Title: gnome-shell consistently using 25% CPU Status in gnome-shell package in Ubuntu: Incomplete Bug description: AM consistently seeing gnome-shell taking 20-30% cpu range. No extensions installed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2.2 ProcVersionSignature: Ubuntu 6.5.0-1023.24-oem 6.5.13 Uname: Linux 6.5.0-1023-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 12:44:10 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-01-17 (232 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.9-0ubuntu8 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2079042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
