Bug 486074

Summary:	Baloo write like crazy and freeze system
Product:	[Frameworks and Libraries] frameworks-baloo	Reporter:	Guo Yunhe <i>
Component:	Baloo File Daemon	Assignee:	baloo-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	tagwerk19
Priority:	NOR
Version First Reported In:	6.1.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	baloo write disk like crazy

Description Guo Yunhe 2024-04-24 14:11:58 UTC

Created attachment 168871 [details]
baloo write disk like crazy

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
The system was installed months ago. In theory, Baloo has indexed most files on the disk. But recently, I experienced frequent system freeze. When looking into system monitor, the only strange thing is that Baloo writes data to disk like crazy. (see attachment) I was playing Steam game Grand Theft Auto V at the moment. And most system freeze happened when I play Steam games. Probably Baloo is indexing SteamLibrary folder which contains lot of huge data files (but not many in number, I configured to not index file content). After killing Baloo and stop it from running in backend, I didn't have any system freeze anymore.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20240419
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C94
System Version: 1.0

ADDITIONAL INFORMATION

Comment 1 tagwerk19 2024-04-25 07:15:01 UTC

Strange....

Writes from baloo_file, rather than baloo_file_extractor, imply loads of file name/metadata changes, possibly loads of deletions (which might also come from loads of folder renames).

To hammer your system with writes, it would have to be "really loads"

I'd be tempted to exclude the Steam folders from indexing or be careful if you've decided to index hidden files (cached files?). If you wish, you could try inotifywait and see what baloo_file is trying to keep up with (Bug 455606).

Comment 2 tagwerk19 2024-08-17 14:20:01 UTC

Did you find anything? Did you try excluding the Steam folder?

Comment 3 Bug Janitor Service 2024-09-01 03:47:22 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Bug Janitor Service 2024-09-16 03:46:54 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.