Description of problem: This occurs when I open the "Known Wi-Fi Networks" listing. It seems isolated to when I have a WPA2-Enterprise network configured. gnome-control-center starts taking 99% CPU and mapping absurd amounts of memory (almost 100GB last I checked). strace indicates rapid polling of multiple file descriptors. I induced the SIGABRT to be able to file this report. Version-Release number of selected component: gnome-control-center-3.28.1-2.fc28 Additional info: reporter: libreport-2.9.5 backtrace_rating: 3 cmdline: gnome-control-center --overview crash_function: __poll executable: /usr/bin/gnome-control-center journald_cursor: s=9dee988260b448e6a2bf1661cb7ff49e;i=ddce9;b=d6de6f7260fa411fb5f5d968ef928f71;m=107962bc10;t=56bce042aa5a2;x=f5a09a165f2131f4 kernel: 4.16.6-302.fc28.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1434092 [details] File: backtrace
Created attachment 1434093 [details] File: cgroup
Created attachment 1434094 [details] File: core_backtrace
Created attachment 1434095 [details] File: cpuinfo
Created attachment 1434096 [details] File: dso_list
Created attachment 1434097 [details] File: environ
Created attachment 1434098 [details] File: limits
Created attachment 1434099 [details] File: maps
Created attachment 1434100 [details] File: mountinfo
Created attachment 1434101 [details] File: open_fds
Created attachment 1434102 [details] File: proc_pid_status
I experienced this issue on the previous Fedora release, as well. It sometimes manifests as a freeze of the Control Center interface immediately after saving the configuration of a WPA2-Enterprise network. So, I don't think it's specifically related to the "Known Wi-Fi Networks" interface.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.