Summary: | System ran out of ram while baloo_file_extractor is indexing a huge mbox file | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | Alex Fiestas <afiestas> |
Component: | Baloo File Daemon | Assignee: | baloo-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | me, tagwerk19 |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=443547 https://bugs.kde.org/show_bug.cgi?id=460882 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alex Fiestas
2021-12-30 08:27:38 UTC
Feels like 443547, see: https://bugs.kde.org/show_bug.cgi?id=443547#c1 I don't think there's a trick to get the individual messages indexed separately. (In reply to tagwerk19 from comment #1) > Feels like 443547 I'll flag as a duplicate. I know baloo_file_extractor skips text/html files over 10MB: https://bugs.kde.org/show_bug.cgi?id=410680#c7 There's an argument that it should skip any file over 10MB (or, maybe friendlier, index the first 10MB and then stop) *** This bug has been marked as a duplicate of bug 443547 *** A possibly relevant merge request was started @ https://invent.kde.org/frameworks/baloo/-/merge_requests/231 |