On 12/12/2018 12.17, Anton Aylward wrote:
On 2018-12-11 9:08 p.m., Carlos E. R. wrote:
This single process says it is using 1/4 of a terabyte virtual memory! I know this is not real memory, but still...
Indeed, and that too can be indicative of a memory leak.
Yes, what matters is the working set, but even that may result in paging.
I admit there are some applications that might want to use that 1/4 of a terabyte virtual memory, some photo editing for example, but common use, email, web browsing, regular editing shouldn't. Its not as if you are composing a coffee table book with double A3 page spreads.
Or are you?
No. In fact, I opened yesterday a calc sheet (plus thunderbird, firefox and chrome). Worked just fine.
In this instance, the 'baloo_file' there isn't much CPU activity. It may be that it is running in some CPU-limited framework. If something like this really freaks you out then there us always the possibility of starting it under a ULIMIT-ed shell (see man bashbuiltins)
Supposedly baloo is designed to idle when the machine is busy.
So go back to the 'top' command and see what is /really/ consuming resources, what is thrashing, what is leaking memory.
Well, as I said, I have one terminal running "top" like this: top -o RES -b -n 4000 -d 300 > somefile to log the crash. But tonight, it did not crash. It is working just fine, with the same load that crashed two days in a row. The only thing I did was uninstall btrfsmaintenance. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)