On Monday, Google's Gmail service was unavailable, but a side effect of that was somewhat unexpected; Google's Chrome browser on the desktop started crashing for many users. Users noted that a faulty interaction between the browser and Google's servers was causing the crash and made surfing the web impossible. Chromium, the open source base for the Chrome browser, was also affected.
Google Developer Tim Steele shed light on what had happened. It appears that the Chrome synchronisation service is able to set usage quotas for various data types that synchronise with it. When the problem in the Gmail system occured – a faulty load balancing configuration change is blamed – the synchronisation service switched to a "conservative" reaction mode and told all clients to throttle all data types being synchronised. Not all Chrome browsers implement all available data types though, and when told to throttle a data type it didn't implement, Chrome browsers responded by crashing.
A fix for the client has been committed upstream and the Google engineers are reviewing when it will be merged with the mainstream of Google's Chrome browser releases. The server side issues have already been resolved.
11 December 2012 The H Open
With 20+ years in technical roles and specialized GRC expertise, I translate complex security frameworks into actionable insights. My journey from financial compliance to enterprise security initiatives informs this blog, where I break down cybersecurity concepts for both professionals and everyday users seeking practical protection in our digital world.
Subscribe to:
Post Comments (Atom)
-
Open Paint by clicking the Start button, clicking All Programs, clicking Accessories, and then clicking Paint. Click the Paint button, cli...
-
The Windows logo key, located in the bottom row of most computer keyboards is a little-used treasure. Don't ignore it. It is the shortcu...
-
The technology industry is being ravaged by countless patent-infringement cases between companies that argue their intellectual property...
No comments:
Post a Comment