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

https://bugs.kde.org/show_bug.cgi?id=380456 Stefan Brüns changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d |

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #21 from tagwer...@innerjoin.org --- Created attachment 143869 --> https://bugs.kde.org/attachment.cgi?id=143869=edit pdftotext results from https://ipfs.io/ipfs/QmVqWhPuQkE7reTN5F9TiSeA75z62VNaZUSFZz3FdWTLbC (In reply to Adam Fontenot

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #20 from Adam Fontenot --- (In reply to tagwerk19 from comment #19) > I would still suspect memory use rather than CPU as the underlying reason. It's quite possible that you're right about that. I do know the game is sensitive to available

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #19 from tagwer...@innerjoin.org --- (In reply to Adam Fontenot from comment #18) > Hmm, even assuming this is true, does the process suspend if the user is on > battery? An otherwise idle system consuming 100% of a core for hours on end >

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #18 from Adam Fontenot --- (In reply to tagwerk19 from comment #17) > If you look at htop, you'll see that baloo_file and baloo_file_extractor run > with minimum priority. They'll yield to nearly everything that wants a CPU. > They should

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

https://bugs.kde.org/show_bug.cgi?id=380456 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #16 from Adam Fontenot --- I actually filed an upstream bug with Poppler for its handling of the specific PDF file I was seeing issues with. https://gitlab.freedesktop.org/poppler/poppler/-/issues/1173 Surprisingly, the Poppler devs say

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

https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #15 from DDR --- I second this. It's a bit absurd to just run it with no resource limits, internally or externally. On Wed., Oct. 13, 2021, 11:04 p.m. Adam Fontenot, wrote: > https://bugs.kde.org/show_bug.cgi?id=380456 > > Adam Fontenot

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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