https://bugs.kde.org/show_bug.cgi?id=386791
Bug ID: 386791
Summary: baloo_file_extractor memory leak when indexing GPG
encrypted files
Product: frameworks-baloo
Version: 5.39.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Baloo File Daemon
Assignee: pinak.ah...@gmail.com
Reporter: victor.bouvier-deleau+kdebugtrac...@kolabnow.com
Target Milestone: ---
Created attachment 108810
--> https://bugs.kde.org/attachment.cgi?id=108810&action=edit
Indexing of GPG files
Software:
Arch Linux (fully up to date on 2017-12-11 21:12)
KDE 5.39.0 / Plasma 5.11.3
baloo 5.39.0
Hardware:
i5 3570k
MSI Z77A-G45
8GB DDR3-1600MHz
GTX 1080Ti
Overview:
Ok so, on the left is the output from "balooctl monitor" and as you can see it
just started indexing some GPG encrypted files (android apk backed up with
oandbackup and encrypted using OpenKeychain).
Before that the process was using very little memory, the second output from
"balooctl status" in the top right was made just before indexing of the GPG
encrypted files.
But if you look at the memory amount the process "baloo_file_extractor" takes
in the bottom right you can see that there's a problem. I reruned "balooctl
status" (not shown in screenshot) after and it only showed "Current size of
index is 292,50 MiB" even though KSysGuard is showing 3.8GiB.
If I let baloo go on and index the rest (I tried it a couple of times), the
process "baloo_file_extractor" is eventualy going to take the totality of my
RAM, then my PC will freeze while swaping 6 or so GiB, then baloo is going to
continue to eat the new 6 or so GiB that was just liberated.
--
You are receiving this mail because:
You are watching all bug changes.
