Bug 450406 - baloo_file keeps appearing in coredumpctl
Summary: baloo_file keeps appearing in coredumpctl
Status: RESOLVED FIXED
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: baloo-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-16 20:16 UTC by Antti Savolainen
Modified: 2022-03-21 07:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
backtrace (192.90 KB, application/zip)
2022-02-16 20:16 UTC, Antti Savolainen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antti Savolainen 2022-02-16 20:16:32 UTC
Created attachment 146835 [details]
backtrace

SUMMARY
I don't know why it keeps happening and I don't know how to reproduce it but when I check coredumpctl, baloo_file keeps appearing repeatedly. It seems to be stuck in recursion.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Comment 1 tagwerk19 2022-02-17 07:39:02 UTC
Have you deleted a very large folder? or moved one?

I've found that Baloo can have trouble when clearing up "old records", Bug 437754. It could be that the best way out is to reindex (delete the index with "balooctl purge" and let it rebuild)
Comment 2 Antti Savolainen 2022-02-17 11:30:36 UTC
Like I said, I have no idea what causes these crashes as there's no indicators when it happens. They just crop up in coredumpctl. I'll try 'balooctl purge' and see if it works.
Comment 3 tagwerk19 2022-03-04 08:09:15 UTC
Did the purge and reindex work?

Deleting large folders hits Baloo disproportionally hard.
Comment 4 Antti Savolainen 2022-03-04 16:45:22 UTC
So far I don't see any. I'll notify is I notice it again.
Comment 5 Bug Janitor Service 2022-03-19 04:35:01 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 6 Antti Savolainen 2022-03-20 21:45:14 UTC
Do you think this can be closed? I haven't encountered it after doing the purge or after doing a clean arch install.
Comment 7 tagwerk19 2022-03-21 07:42:24 UTC
(In reply to Antti Savolainen from comment #6)
> Do you think this can be closed? I haven't encountered it after doing the
> purge or after doing a clean arch install.
Thanks! I'm glad the issue has gone...

Maybe worth remembering the issue if you delete a (another?) large folder - see if you get into the same state.