https://bugs.kde.org/show_bug.cgi?id=475975
tagwer...@innerjoin.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #4 from tagwer...@innerjoin.org ---
(In reply to Piotr Keplicz from comment #3)
> The offending file is a Polish dictionary:
That's likely to be a challenge :-)
Baloo will try to set up a record in the index for every word in the
dictionary, with a link to its location in the file. That will be a BIG
transaction. I see baloo_file_extractor start indexing the file but slow to a
crawl, due to the "MemoryHigh=512MB" cap on RAM usage in the kde-baloo.service
unit file. Swap usage goes up quickly, presumably dirty pages waiting to be
committed.
A personal view, I don't think baloo should use swap...
If I change the systemd limits to:
MemoryHigh=50%
MemorySwapMax=0B
and give my test VM 16GB to work in, I see the baloo_file_extractor crash.
Tested on Fedora38 and Neon User. Confirming.
If I try on Neon Unstable, it looks as if baloo skips the content indexing of
the file. A
$ balooshow -x SJP2-202302181714.mobi
just gives...
141b30ed0da2dd 3977093853 1317680 SJP2-202302181714.mobi
[/home/test/Testdir/SJP2-202302181714.mobi]
Mtime: 1698129246 2023-10-24T08:34:06
Ctime: 1698129246 2023-10-24T08:34:06
Internal Info
File Name Terms: F202302181714 Fmobi Fsjp2
XAttr Terms:
Plain Text Terms:
Property Terms: Mapplication Mebook Mmobipocket Mx T5
--
You are receiving this mail because:
You are watching all bug changes.
