| Summary: | `baloo_file` process taking up significant memory | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | drizzt321 |
| Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | tagwerk19 |
| Priority: | NOR | ||
| Version First Reported In: | 5.103.0 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
drizzt321
2023-10-16 17:03:47 UTC
(In reply to drizzt321 from comment #0) > ... I notice `baloo_file` process is taking up a relatively large amount of memory... See if you are having problems with changing minor device numbers - possible if you are running BTRFS. In that case, Baloo can see files "reappear" after a reboot with a different ID and reindex them. You can check with "baloosearch -i one-of-your-files" and see if you get multiple results. The "-i" shows the internal DocID that baloo uses. If you get multiple results, then that might explain the larger index... In general baloo pulls pages form its index into memory "as needed" and "for reading", when indexing a new file the changes to the index are bundled into a transaction and the database pages marked "dirty" ready to be written when the transaction is committed. If you are not writing, the pages can be dropped when anything else wants the memory. There's been a relatively change to the memory limits (as set in the systemd unit file for kde-baloo) to cap the memory usage to 512M: https://invent.kde.org/frameworks/baloo/-/merge_requests/124 maybe this is hasn't reached Debian (In reply to drizzt321 from comment #0) > ... But now I notice `baloo_file` process is taking up a relatively large amount > of memory, which is obviously concerning ... Are you still seeing this? If so check to see what "systemctl --user status kde-baloo" says... Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |