Joel Lee writes:
After five long years of using Chrome as my main browser, I finally had to bite the bullet and switch over to Firefox due to some glaring issues
In my case, it was the high memory and CPU usage that finally frustrated me to the point of no return.
I have an ongoing process (WIRE) that requires about 30% of memory, and causes Chrome to freeze. The Task Manager provided by developers (above) does not provide a workable solution.
The need to reset the application using
Ctl-Alt-F3 killall chrome
gets tiresome quick.
And so here we are.