google-chrome
When I switch between windows or tabs (Chrome, PHPStorm), the rendering of the page doesn't complete. It looks like the screenshot below and only changes when I resize the window or scroll down.
Playing video's is not a problem, so it's not just about slow rendering.
I've got no clue how to debug this problem. How can I find out what's the actual problem?
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.
This is a known issue with ATI/AMD graphics card and compositing.
For some people starting Chrome with --blacklist-accelerated-compositing parameter brings some help. Others report that --disable-gpu parameter helps.
See http://code.google.com/p/chromium/issues/detail?id=136054
As far as i understand, the only real fix is to switch to Nvidia or Intel GPU. Adding parameters like the ones above cost performance and disable certain features which require compositing. To check your Chrome's state of GPU affairs visit chrome://gpu
Best Answer
I found this bug report. It looks like there is a feature called virtual contexts that is causing problems with Intel MESA drivers.
This is the code review for the respective regression.
UPDATE (10/16/2015):
This fix is available in Chrome Dev (48.0.2535).