Created attachment 157025 [details] Backtraces generated by gdb and drkonqi-coredump-gui SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** baloo_file_extractor crashes and the coredump take too much space (in /var/lib/systemd/coredump), I attached some backtraces generated by drkonqi and gdb, but feel free to ask for more details STEPS TO REPRODUCE 1. Use Baloo 2. It crashes and ends up producing several Gb of coredumps after some time OBSERVED RESULT The program crashes and generates too much coredumps EXPECTED RESULT The program doesn't crash or at least generates a limited amount of dumps SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.2.1-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION
Looks similar to Bug 466760 ... ... and there might be a connection to Bug 465801 that affects baloo on Wayland. Try logging in with X11 and see if the same happens.
Possible that this is fixed with Frameworks 5.104 (Bug 465801)
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!
It is (In reply to tagwerk19 from comment #2) > Possible that this is fixed with Frameworks 5.104 (Bug 465801) It is indeed fixed (I mean it's an old report, but it seems like the bug is not there since this version)