https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260029

--- Comment #10 from Jesper Schmitz Mouridsen <[email protected]> ---
(In reply to Jesper Schmitz Mouridsen from comment #9)
Unmodified The interval of the QTimer m_updateTimer CGroupDateModelPrivate is
zero when it is started in setEnabled, the problem is that
https://github.com/KDE/libksysguard/blob/ff14c3b7086d3dcdce479b5041947a739904374d/processcore/cgroup_data_model.cpp#L110
returns before changing the default zero interval to 2000 ms.. It turns out
even a not connected to QTimer::timeout a started QTimer with interval 0 causes
high cpu usage..

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to