If you are an unhappy user of Chromium-browser or chrome you know exactly what I’m talking about. I stopped to count how many time I had to reboot my whole system because these two guys. Yeah, I’m guilty in part. Since I often have 30 tabs in my browser. But, shouldn’t these guys handle with memory resource in a more clever way? Recently I read that the new way Chrome is deal with it is to kill tabs that reach a limit amount of memory, but it’s not a happy end at all.
In my system, Linux Mint (currently), I just lost my counts the times I had to reboot all the system because The Memory Eater.
For now , seems it hasn’t any solution, but I realized these guys have a chrome://memory-redirect tool [1], that show you how many memory are in using. Take a look at the s-shot.

While any real solution comes, how about to keep an eye in who is the greedy memory guy and close it :).
Resources:
[1] https://www.chromium.org/developers/memory-usage-backgrounder
Read Full Post »