| Summary: | Memory Leak when using the search function | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | kbrea |
| Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | nate, plasma-bugs-null, stefan.bruens |
| Priority: | NOR | ||
| Version First Reported In: | 5.42.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
kbrea
2018-01-21 23:22:54 UTC
Your analysis is wrong: Although baloorunner reserves a memory window of 256 GByte, it does not actually use this amount of memory in terms of physical memory. The window is used to be able to map its database file, even when this database grows beyond its initial size. As baloofile uses the same database, and also has to map it to write updates, the same applies to baloofile. Whatever is crashing you computer/desktop, its not this memory reservation. It may be a database corruption (happens more frequently when users just kill processes while these are active), try renaming/deleting the baloo database. Stefan, if you need information from the reporter, you should clarify which :) |