https://bugs.kde.org/show_bug.cgi?id=386791
Stefan Brüns <stefan.bru...@rwth-aachen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
CC| |stefan.bruens@rwth-aachen.d
| |e
--- Comment #4 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
(In reply to Victor Bouvier-Deleau from comment #3)
> Ok so the steps to reproduce the bug without having access to my files would
> be:
> 1. Create a lot of GPG encrypted files that would amount for 1GiB or so
> 2. Place them somewhere in the /home/<user> directory
> 3. Restart the computer
> 4. Run thop/open ksysguard to monitor memory usage on baloo_file_extractor
> process
> 5. Run "balooctl monitor" to monitor the indexing process in order to know
> when it will begin indexing those encrypted files
> 6. Watch the memory consumption go through the roof as soon as baloo start
> indexing the encrypted files while balooctl status doesn't report that
> amount of memory used by the index
>
> If you want me to do more diagnostic on my end, ask away!
The file is equivalent to e.g. the output of the following?
$> dd if=/dev/zero bs=1k count=1000 | gpg2 -a -e -o foo.gpg -r <myself>
Although the file is "text", as it is plain ASCII, baloo obviously should skip
it when doing the content-indexing step.
--
You are receiving this mail because:
You are watching all bug changes.
