First one is a blocking property getter in Monitor::balooStarted: slotIndexerStateChanged(m_scheduler->state()); The other one is implicit coercion of a QDBusPendingReply to its result type in Monitor::updateRemainingTime: auto remainingTime = m_scheduler->getRemainingTime(); if ((remainingTime != m_remainingTimeSeconds) && (remainingTime > 0)) { These calls can cause the main loop of the KCM & other consumers to freeze if the daemon is busy, and increases latency in normal circumstances.
A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/197
Git commit 8c11e0290d2a7713d6c627e42ea56c92047acd7b by Janet Blackquill. Committed on 16/05/2024 at 16:07. Pushed by jblackquill into branch 'master'. qml: don't do blocking DBus calls in Baloo.Monitor This makes the experience more responsive, especially if the system is under load. M +33 -7 src/qml/experimental/monitor.cpp https://invent.kde.org/frameworks/baloo/-/commit/8c11e0290d2a7713d6c627e42ea56c92047acd7b