https://bugs.kde.org/show_bug.cgi?id=490685
--- Comment #6 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- Created attachment 172018 --> https://bugs.kde.org/attachment.cgi?id=172018&action=edit dolphin flamegraph A flamegraph seems really helpful here, although the issue is *not* CPU use (<20% of one core). Dolphin is spending almost all its CPU time in `KBuildSycoca::recreate` via KService::serviceByDesktopName -> Ksycoca::ensureCacheValid -> KSycocaPrivate::checkDatabase Looking at backtraces in gdb, it looks like we hit `DolphinMainWindow::updateOpenPreferredSearchToolAction` over and over again. There could be a loop here? https://invent.kde.org/system/dolphin/-/blob/master/src/dolphinmainwindow.cpp#L228 If this function is run whenever the sycoca database changes, but the function itself is capable of triggering a database refresh if KSycoca says the database is invalid (e.g. maybe because a bad string comparison using the file path with a trailing slash??), then it could potentially loop? Speculation on my part. -- You are receiving this mail because: You are watching all bug changes.
