Created attachment 1696014 [details] strace -tt -s 500 Description of problem: Every few hours goa-identity-service starts some loop in communicating with SSSD KCM. CPU time usage hits 100%, indicating some kind of busy loop. Uppermost two lines from 'top': PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 827922 root 20 0 64156 51484 9324 R 78,9 0,2 232:44.39 /usr/libexec/sssd/sssd_kcm --uid 0 --gid 0 --logger=files 884600 zdzichu 20 0 389316 12516 10664 S 15,8 0,1 1:34.36 /usr/libexec/goa-identity-service It looks like SSSD-KCM use more CPU, but I've observed following: 1) if I kill sssd_kcm, it get restarted and CPU usage spike again 2) if I kill goa-identity-service, CPU usage dissappears So I conclude that GOA is constantly asking KCM for something. CPU usage for KCM is only observable when goa communicates with it. Version-Release number of selected component (if applicable): sssd-kcm-2.3.0-1.fc32.x86_64 gnome-online-accounts-3.36.0-1.fc32.x86_64 How reproducible: Happens at least 4 times a day. Steps to Reproduce: 1. Use computer normally. 2. 3. Additional info: 3 seconds of stracing goa-identity-service attached.
Same here with sssd-kcm 2693 root 20 0 255940 32592 9536 S 40.3 0.2 5:42.16 /usr/libexec/sssd/sssd_kcm --uid 0 --gid 0 --logger=files
Still happening with gnome-online-accounts-3.37.90-1.fc33.x86_64 I think this may be https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/79
I can confirm this is still happening on Fedora 33 Silverblue. gnome-online-accounts-3.38.0-1.fc33.x86_64
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This is still an issue on Fedora 34.
*** This bug has been marked as a duplicate of bug 1645624 ***
This isn't a dupe of bug 1645624. This bug is (one of) the causes of that bug. (sssd_kcm's high CPU usage because it's being spammed with requests from goa-identity-service). This can be observed by sending SIGSTOP to goa-identity-service and seeing that sssd_kcm goes idle. Then send SIGCONT and see that it's chewing CPU again. The upstream bug is https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/79#note_1603051 - that link takes you my reproducer. This bug is present in Fedora 36 and 37.