You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm on F37 Silverblue with conmon-2.1.2-3.fc37.x86_64, but this was happening on F36 as well. Conmon seems to be stuck eating 100% of a CPU core quite frequently with my fedora-toolbox-36, and I have to quit everything running from that toolbox to make conmon exit. I'm not sure what exactly triggers the issue, might be going in and out of suspend. I tried to investigate what it's doing with gdb, but there was nothing outright suspicious; it seemed as though one thread of the process was stuck busy-polling/iterating the glib context.
The text was updated successfully, but these errors were encountered:
I'm on F37 Silverblue with conmon-2.1.2-3.fc37.x86_64, but this was happening on F36 as well. Conmon seems to be stuck eating 100% of a CPU core quite frequently with my fedora-toolbox-36, and I have to quit everything running from that toolbox to make conmon exit. I'm not sure what exactly triggers the issue, might be going in and out of suspend. I tried to investigate what it's doing with gdb, but there was nothing outright suspicious; it seemed as though one thread of the process was stuck busy-polling/iterating the glib context.
The text was updated successfully, but these errors were encountered: