https://bugs.kde.org/show_bug.cgi?id=404057
--- Comment #48 from tagwer...@innerjoin.org --- (In reply to Martin Steigerwald from comment #0) > 3. If you like to kick it beyond any sanity: > - have it go at the results of git clone > https://github.com/danielmiessler/SecLists.git > - here it eats the resources of a quite potent laptop with 16 GiB of RAM > as if there was no tomorrow. For completeness, I thought it would be worth revisiting this. I downloaded and extracted master.zip (660MB download, extracts to about 2GB). I tested in a guest VM, Neon User edition, BTRFS, 8 GB RAM. I ended up setting MemoryHigh=50% and MemorySwapMax=0, I think with *very* *large* number of different words as is definitely the case here, you are going to be hammering Baloo and it is going to need space. It reached 3.8G memory usage and bounced around for a while just under that level, dropping down again when the indexing finished. Rebooting the system did not trigger any reindexing (I didn't set up any snapshots). I didn't manually unzip files within the bundle (the zip bombs). I don't know if Baloo ever tried to unpack zipped files, if so these could have been nasty.... It looks OK. I had six files where Baloo refused with an "Invalid Encoding". The indexing completed in around 10 min. The index file was about 2G. The system remained fully usable during the indexing. I think we can say "Thankfully, that's fixed" and the call can remain closed :-) -- You are receiving this mail because: You are watching all bug changes.
