[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Nick Cross changed: What|Removed |Added CC||k...@goots.org -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Vishesh Handa changed: What|Removed |Added Assignee|m...@vhanda.in|pinak.ah...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Martin Senftleben changed: What|Removed |Added CC||li...@drmartinus.de --- Comment #45 from Martin Senftleben --- I'm not sure if it's wise to add to this thread, but the topic is the same: for three days now baloo_file_extractor is, according to my ksysguard, the top RAM and particularly swap memory eater. The most peculiar, but maybe normal thing is, that it doesn't eat up all RAM (I have 16 GB installed, but bsysguard shows only 9 GB being used), but feeds on swap memory. The swap file is now at its limit (6.3/6.3 GB) and the machine is slowing down. I tried various commands mentioned here, all failed on my machine or produce no usable output: "ps aux | grep baloo_file_extractor" produces: "username 3076 43.5 49.3 272558692 8087596 ? DNl Okt24 3018:54 /usr/bin/baloo_file_extractor username 3575 0.0 0.0 10776 2016 pts/1S+ 12:03 0:00 grep --color=tty -d skip baloo_file_extractor" and "sudo echo 3 > /proc/sys/vm/drop_caches" (in the hope that this might clear up space) produces: "Keine Berechtigung" (= no permission) Other things I didn't try. I run Manjaro Arch-Linux up-to-date, 64 bit. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 Brendon Higgins changed: What|Removed |Added CC||bren...@quantumfurball.net --- Comment #44 from Brendon Higgins --- Does the "avoid indexing large text files" hack in extractor/app.cpp (which in master has a 10 MB limit) still work if the text file starts small but happens to rapidly grow large from another process at the same time it is being indexed? I had a simulation running that appended (a lot of) numeric data to an initially empty text file, and by my observation it seemed like baloo blew up on it. I'm unfamiliar with baloo's code, but taking a glance at it (particularly app.cpp) suggests to me that this scenario might be possible. On a separate machine, and maybe a separate issue, I noticed baloo_file_extractor running for a long time with significant RAM usage (>2GB) that did not decline until it had apparently finished indexing a few thousand files that I had recently changed. Why would it need to hold so much RAM as it goes from one file to the next? In the source I notice a database handler that seems to persist for the entire batch (this is even marked with a FIXME). Could there perhaps be a leak in that? -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421 --- Comment #43 from John Andersen --- Replacing dead link in above reply: http://osdir.com/ml/kde-commits/2014-05/msg02993.html This is becoming a very debilitating limitation for me. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 332421] Baloo file extractor ate all my PC's RAM
https://bugs.kde.org/show_bug.cgi?id=332421
John Andersen changed:
What|Removed |Added
CC||jsam...@gmail.com
--- Comment #42 from John Andersen ---
Apparently the hack installed back in August of 2014 to prevent indexing
anything but .txt file under 50 Meg is still resident in some packages of
extractor/app.cpp:
if (mimetype == QLatin1String("text/plain")) {
+ if (!url.endsWith(".txt")) {
+ mimetype.clear();
+ }
+
+ QFileInfo fileInfo(url);
+ if (fileInfo.size() >= 50 * 1024 * 1024 ) {
+ mimetype.clear();
+ }
See:
http://webcache.googleusercontent.com/search?q=cache:LUTPrh1zmZ8J:r.git.net/kde-commits/2014-05/msg02993.html+&cd=4&hl=en&ct=clnk&gl=us
I would like to index a whole boatload of source code, but because it does not
have a file extension of .txt the extractor fails, so then Baloo gets nothing
to index.
It works fine on KDE4, but on Plasma 5 version 15.12.0 (Manjaro / Arch) I
can't index any plain text files that do not end with an extension of .txt.
--
You are receiving this mail because:
You are watching all bug changes.
