plasma-systemmonitor 100% CPU and 100% memory, every other time it runs?

[chconnor]

Edit: bug filed.

Just stumbled across this... If I run the system monitor (meta-esc for me, or plasma-systemmonitor on the CLI), it works every other time.

The time it does not work, it seizes up the system: 100% use of a CPU and the memory usage quickly maxes out (16GB in my case). The system basically freezes up if I don't kill it immediately, necessitating a kill of the process via ssh client. Then it takes a minute or two for things to calm down and be usable again.

Then I run it again and it works fine. Then I run it again and it's not. Rinse/repeat.

Anyone seen this? I did some googling and found a variety of not-quite-the-same things, but haven't looked too hard yet.

I note that stdout is slightly different on a successful vs. not successful run:

Last four lines of success:

qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "implicitHeight"
QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/libexec/ksysguard/ksgrd_network_helper") is still running.
org.kde.ksysguard.plugin.network: Helper process terminated abnormally: ""
"There are still \"5\" items in the process of being created at engine destruction."​

Last three lines of failure:

qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:344:18: QML ScrollView: Binding loop detected for property "implicitHeight"
QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/libexec/ksysguard/ksgrd_network_helper") is still running.
org.kde.ksysguard.plugin.network: Helper process terminated abnormally: ""​

Nothing shows up in the journal when this happens (besides what you'd expect in terms of things complaining about limited system resources). There were some "Pageflip timed out" errors one time...