ATTENTION!
The description below applies to Google Chrome. For Chromium instead of ~/.config/google-chrome
you have ~/.config/chromium
!
In ~/.config/google-chrome/
you will see your profile folders. Let's say, you have beside the default (named Default
) an another one called d3vid
which you want to make default.
I give you two options:
Rename the Default to something else, and your profile to Default:
mv Default Default_old; mv d3vid Default
Move Default to a better name, and create a symlink to your preferred profile:
mv Default My_cool_profile; ln -s ~/.config/google-chrome/d3vid ~/.config/google-chrome/Default
After a lot of investigating, re-installing Chrome, purging options, etc. I found the problem is caused by the internal flash of Chrome in the latest release. Very easy to fix.
First off go to the URL bar and enter about:plugins
and press enter. This will bring up the plugins screen. Once there click on the plus icon next to Details to display all plugin details.
Scroll down till you find Adobe Flash Player
, it should say 2 files, meaning you have Flash player installed separately in the system. Either way find the first one in the list libpepflashplayer.so
and disable this one. If there is a second one /usr/lib/adobe-flashplugin/libflashplayer.so
do NOT disable the second one.
Once done you can go to:
http://get.adobe.com/flashplayer/
And install the latest version of flash for your system, in this case the page will tell you to download Flash for Firefox if you have it installed, yes this is what you want.
Download and install, in my case I already had Flash installed for FF so it worked immediately no need to install anything else.
Once done, restart Chrome and it works perfectly. Something seems to be wrong with flash for Chrome in the most recent build, so gonna have to leave it off until they fix it.
Best Answer
Well, since Google chrome opens a new processes for each new tab, it may be related to limitations of using a low powered cpu notebook in that situation. For example, in firefox, since each new tab will run off of generally the same processes, there won't be a huge leap in resource usage when opening a new tab. Chrome, on the other hand, uses a seperate process for each new tab or new site (depending on your configuration), and also a separate process for things like plugins for audio and flash. As a result, opening new tabs may have a higher initial cost, which may really become evident on a low power processor like a notebook.
Personally, where chrome isn't a great fit, I tend to devolve back to firefox since it (currently) works on close to a single process model and will tend to be easier on resources as a result (though more prone to sites crashing your session, etc).