Chrome browser beta release 34 includes the google 'Aura' compositor that caused lots of issues on my env using 12.04 with GPU = intel HD4000.
So, i went back to the 'Chrome-browser' general release and stopped using 'chrome-beta' which i always liked.
Prior to chrome-beta 34 everything with the GPU with WebGL with the GPU drivers was fine.
I do not understand the implications of Google's move to 'aura' compositor on my choice of browser ( chrome or chromium ) for my ubuntu system.
I can just install Chromium browser and try it for awhile and see whether i like it better than chrome browser.
But i am interested in this source divergence around the google 'Aura' compositor and what actually would work better on my linux system??
If google are doing something (fundamental in the aura compositor) with the way that their browser interacts with X or with GTK i have no idea what i should check in my system to make sure that i have not gummed something up.
I did originally have to twiddle some hardware driver things in Ubuntu in order to get WebGL to work with my GPU (intel HD4000 drivers).
--EDIT-- google-chrome-unstable (M35 including aura) is running fine detls below:
remove older package (stable or beta)
install google-chrome-unstable using apt
open broswer to "chrome://flags" changing first option to "ignore blacklist"
everything looks OK in "chrome://gpu" following tweek above