baloo_file_extractor uses more than 1Gb of memory. Sometimes it spikes up, filling the 4Gb of RAM available and thereby freezes the system. Most of the memory used is private, with 0.5Gb coming from the heap, and 0.5Gb from ~/.local/share/baloo/index. Slightly more than 0.5Gb is marked as dirty. The following is the output of ps aux and balooshow: [user@computer ~]$ps aux | grep baloo_file_extractor user 627 3.8 26.6 6221380 1056780 ? SNl 15:21 0:09 /usr/bin/baloo_file_extractor user 657 0.0 0.0 11000 2184 pts/1 S+ 15:25 0:00 grep baloo_file_extractor [user@computer ~]$ balooshow 627 657 The fileID is not equal to the actual Baloo fileID This is a bug GivenID: 627 ActualID: 0 GivenINode: 0 ActualINode: 0 GivenDeviceID: 627 ActualDeviceID: 0 No index information found The fileID is not equal to the actual Baloo fileID This is a bug GivenID: 657 ActualID: 0 GivenINode: 0 ActualINode: 0 GivenDeviceID: 657 ActualDeviceID: 0 No index information found
Could you please provide the Baloo version number?
Hello! This project has been replaced with a newer system so I will be closing this bug. If you could please re-test on the latest Baloo. If the issue still present, please open a new bug under "frameworks-baloo". Thank you!
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 set the bug status 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!
Dear Bug Submitter, 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!