

If that's the case, flushing the DNS cache on your Windows PC should help.

"No, most of us are on Stable/Enterprise channel, and therefore shouldn't have ours messed with at all.Before you try anything complicated, start with the basic fixes. "Are we running Beta/Dev/Canary versions of Chromium where those experiments should take place?" asked one user. Many IT admins are still unhappy though, and are petitioning Google to let them turn off all experimental flags for Chrome to avoid it happening again. The update should have reached all users now, but if you're still having problems or haven't received it, you can also solve the problem by visiting chrome://flags and disabling both chrome://flags/#web-contents-occlusion and chrome://flags/#calculate-native-win-occlusion. Google has now rolled back the WebContents Occlusion change, and Google software engineer David Bienvenu advised affected users to update and relaunch the browser. Do you understand how many hours of resources were wasted by your 'experiment'? Not acceptable." How to fix it We are running professional services for multi million dollar programs. "Do you see the impact you created for thousands of us without any warning or explanation?" one angry business user posted on the Chrome bug tracker.
