https://bugs.kde.org/show_bug.cgi?id=373489
Bug ID: 373489
Summary: runaway CPU (88%) and memory (30MB/s)
Product: plasmashell
Version: 5.8.4
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Task Manager
Assignee: h...@kde.org
Reporter: nev...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Kde is fine, the bug is relatively rare and I do not have a definitive way to
reproduce.
It seems, on a coincidence of 2 times that I can attest (others being
forgotten) that clicking on a grouped sest of windows in the task manager can
lead to a runaway plasmashell main thread (other slave threads to not run
away).
I have a core dump and I have several backtraces. Sometimes I catch a dbus
request being made as evidenced by a dbus connection thread, but I generally
just catch main in:
#0 0x00007fd404d892b5 in QV4::PersistentValueStorage::allocate() () at
/usr/lib64/libQt5Qml.so.5
#1 0x00007fd404d898f2 in QV4::PersistentValue::set(QV4::ExecutionEngine*,
QV4::Value const&) ()
at /usr/lib64/libQt5Qml.so.5
#2 0x00007fd404e0027a in
QV4::QObjectWrapper::method_connect(QV4::CallContext*) () at
/usr/lib64/libQt5Qml.so.5
#3 0x00007fd404dae32b in QV4::BuiltinFunction::call(QV4::Managed const*,
QV4::CallData*) () at /usr/lib64/libQt5Qml.so.5
#4 0x00007fd404e1baeb in QV4::Runtime::callProperty(QV4::ExecutionEngine*,
int, QV4::CallData*) ()
at /usr/lib64/libQt5Qml.so.5
Sometimes I catch main in a QML garbage collection. All other threads are
waiting on the poll sys call and not using CPU.
--
You are receiving this mail because:
You are watching all bug changes.
