https://bugs.kde.org/show_bug.cgi?id=470382
--- Comment #10 from tagwer...@innerjoin.org --- (In reply to Ovear from comment #9) > Memory: 584.4M (high: 512.0M available: 0B peak: 584.9M) You can see Baloo is pushing at the limit, the system has given it a bit of leeway but it not going to carry on doing it... > Memory: 1.3G (high: 31.2G available: 5.7G peak: 3.0G) ... and 512M really wasn't enough 8-/ I'm chasing up an issue elsewhere where it seems that it you have a large index, a "large delete" requires a disproportionate amount of memory. See https://bugs.kde.org/show_bug.cgi?id=380456#c29 and following discussion. > I assumed this might be due to baloo indexing some files that require more > memory. I am trying to isolate and reproduce this issue and will update once > I make progress. No doubt that's possible, there are things like .mbox files (GB's of stored emails in a single file, with encoded attachments 8-) > PS: I have tried creating small text files, and baloo works with the default > MemoryHigh settings currently. Any advice or hints to isolate this problem > would be greatly welcomed. Checking whether it's baloo_file or baloo_file_extractor that takes the memory would be an initial hint (as discovered in 380456 above) -- You are receiving this mail because: You are watching all bug changes.
