https://bugs.kde.org/show_bug.cgi?id=479321
--- Comment #3 from Freddie Witherden <fred...@witherden.org> ---
It is easy to reproduce on my 14 core (20 thread) system when the "Process"
view is open. Monitor chews up an entire CPU core and is entirely
unresponsive. Attaching `perf` and checking the results we find:
5.35% plasma-systemmo libQt6Core.so.6.7.2 [.]
0x00000000002e0525
5.34% plasma-systemmo libQt6Core.so.6.7.2 [.]
0x00000000002e0552
4.68% Thread (pooled) libc.so.6 [.] malloc
4.28% plasma-systemmo libQt6Core.so.6.7.2 [.]
QObjectPrivate::maybeSignalConnected
4.09% plasma-systemmo libQt6Core.so.6.7.2 [.]
0x00000000002e0520
4.01% plasma-systemmo libQt6Core.so.6.7.2 [.]
0x00000000002e0465
1.40% plasma-systemmo libQt6Core.so.6.7.2 [.]
0x00000000002e05e3
1.21% Thread (pooled) libc.so.6 [.] cfree
0.96% Thread (pooled) libQt6Core.so.6.7.2 [.]
QCoreApplication::postEvent
0.92% Thread (pooled) libc.so.6 [.] __tfind
0.87% Thread (pooled) libglib-2.0.so.0.7800.6 [.]
g_main_context_wakeup
0.74% Thread (pooled) libQt6Core.so.6.7.2 [.]
QObject::~QObject
Another item I found when digging through the call graph is
QAbstractItemModel::dataChange. This suggests it is UI related.
--
You are receiving this mail because:
You are watching all bug changes.
