[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 Nate Graham changed: What|Removed |Added Component|Baloo File Daemon |balooctl -- You are receiving this mail

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 tagwer...@innerjoin.org changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 Adam Fontenot changed: What|Removed |Added CC||adam.m.fontenot+kde@gmail.c

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 tagwer...@innerjoin.org changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 soredake changed: What|Removed |Added CC||ndrzj1...@relay.firefox.com -- You are receiving

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 medin changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #5 from medin

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 tagwer...@innerjoin.org changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 --- Comment #4 from Martin Steigerwald --- I helped, but not as much as with your setup: % ~/.local/share/baloo> balooctl indexSize File Size: 8,12 GiB Used: 79,78 MiB PostingDB: 1,36 GiB 1743.970 % PositionDB:

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 --- Comment #3 from tagwer...@innerjoin.org --- (In reply to Martin Steigerwald from comment #2) > % balooctl indexSize > File Size: 8,12 GiB > Used: 77,17 MiB There's some analysis/discussion/confusion about the percentages here:

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #2 from

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 tagwer...@innerjoin.org changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving

[frameworks-baloo] [Bug 437754] "balooctl status" can trigger high memory use

https://bugs.kde.org/show_bug.cgi?id=437754 --- Comment #1 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #0) > It's quite likely that creating so many files so quickly hits the > inotify "event limit" and baloo doesn't get told of all the new files. Creating the testfiles