[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2019-10-17 Thread Savor d'Isavano
https://bugs.kde.org/show_bug.cgi?id=380456 Savor d'Isavano changed: What|Removed |Added CC||anohigisa...@gmail.com --- Comment #13 from

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2019-01-07 Thread soredake
https://bugs.kde.org/show_bug.cgi?id=380456 soredake changed: What|Removed |Added CC||fds...@krutt.org -- You are receiving this mail

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-12-05 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=380456 Reuben changed: What|Removed |Added CC||reube...@yahoo.com -- You are receiving this mail

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-12-04 Thread Johannes Tiemer
https://bugs.kde.org/show_bug.cgi?id=380456 Johannes Tiemer changed: What|Removed |Added Version|5.34.0 |5.52.0 Platform|Neon Packages

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-09-29 Thread Johannes Tiemer
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #11 from Johannes Tiemer --- After excluding the above mentioned folders with lots of small files, baloo stopped its memory eating behavior. Scanning for file numbers and sizes and then warning might be a simple safeguard maybe? -- You

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-09-28 Thread Johannes Tiemer
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #10 from Johannes Tiemer --- I checked. It took baloo_file_extractor 9 minutes (according to uptime) to fill 13GiB RAM, where it pretty much exclusively (as far as I could tell) operated on my Archive disk, which, among others, contains

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-09-27 Thread Johannes Tiemer
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #9 from Johannes Tiemer --- D'oh, forgot to mention: CPU load is 100% on one single core until I kill the process. I'll remember to look into what it's indexing when I boot next time. -- You are receiving this mail because: You are

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-09-27 Thread Johannes Tiemer
https://bugs.kde.org/show_bug.cgi?id=380456 Johannes Tiemer changed: What|Removed |Added CC||jtie...@gmail.com --- Comment #8 from

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-09-11 Thread Allan Andersen
https://bugs.kde.org/show_bug.cgi?id=380456 Allan Andersen changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-03-07 Thread DDR
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #6 from DDR --- > Please report memory usage when indexing is done. I'm really curious to see > that. About 1.1GiB, ~5% of the available system memory. Very reasonable. > Did you kill it? Probably not. I've

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-03-07 Thread DDR
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #5 from DDR --- OK, so I have just discovered the magic of ls -la /proc/1234/fd, where 1234 is the pid of baloo_file_extractor.  baloo_file_extractor was busy on a 1.5GiB text file, production-aria-tables.sql,

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-02-01 Thread Michael Heidelbach
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #4 from Michael Heidelbach --- (In reply to DDR from comment #2) Commands such as ` balooctl index > * ` are unresponsive until I've killed the process. Please clarify 'unresponsive': Did you have to Ctrl-C? You did this

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-02-01 Thread Michael Heidelbach
https://bugs.kde.org/show_bug.cgi?id=380456 Michael Heidelbach changed: What|Removed |Added CC||ottw...@gmail.com ---

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-01-27 Thread DDR
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #2 from DDR --- Comment on attachment 110170 --> https://bugs.kde.org/attachment.cgi?id=110170 Upon killing baloo_file_extractor, I suddenly have a lot more free memory. baloo_file_extractor always seems to use

[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor

2018-01-27 Thread DDR
https://bugs.kde.org/show_bug.cgi?id=380456 DDR changed: What|Removed |Added CC||robertsdavid...@gmail.com ---