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
Founded in 1991, Future Quest Technologies was created based on a fresh consumer need: on-site technology delivery. Future Quest Technologies strove to be, and successfully became, a trusted provider of Information Technology products, services and support. Customers are comfortable knowing they have knowledge, expertise and commitment behind my technology recommendations.
Subscribe to:
Post Comments (Atom)
-
It’s a little more complicated than just copying data By Barbara Krasnoff Sep 2, 2020, 4:35pm EDT Two-factor authentication (2FA) is ...
-
A recent update to Windows Defender gave it the ability to download files through a command line tool. A recent update to the built-in antiv...
-
MARSHALL GUNNELL @marshall_g08 SEPTEMBER 1, 2020, 10:24AM EDT One of the first rules of cyber security is to always lock your PC before s...
No comments:
Post a Comment