Bug 466916

Summary: baloo_file_extractor crashes and the coredump take too much space
Product: [Frameworks and Libraries] frameworks-baloo Reporter: bachirgiga <bachirgiga>
Component: Baloo File DaemonAssignee: baloo-bugs-null
Status: RESOLVED WORKSFORME    
Severity: crash CC: tagwerk19
Priority: NOR    
Version: 5.103.0   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Backtraces generated by gdb and drkonqi-coredump-gui

Description bachirgiga@gmail.com 2023-03-05 21:28:51 UTC 
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
Comment 1 tagwerk19 2023-03-05 23:23:33 UTC 
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.
Comment 2 tagwerk19 2023-03-20 19:11:42 UTC 
Possible that this is fixed with Frameworks 5.104 (Bug 465801)
Comment 3 Bug Janitor Service 2023-04-04 03:45:25 UTC 
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!
Comment 4 Bug Janitor Service 2023-04-19 03:45:50 UTC 
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!
Comment 5 bachirgiga@gmail.com 2023-05-17 22:45:24 UTC 
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)