There's nothing special in the fact that this problem involved a cloud service, or a bundled feature that some users may consider non-essential (all desktop bro

There's nothing special in the fact that this problem involved a cloud service, or a bundled feature that some users may consider non-essential (all desktop browsers are shock-full of such features... unless you count Lynx). Consider this: Google might have pushed a regular Chrome-stable update containing a bug that would make the browser crash frequently for many users. Would that mean there's some fault in the process because Google has the privilege to push updates to the core browser? The fact is, there no much difference, Google "trusts itself" to update any aspect of Chrome, from the code that runs in your machine to any cloud services it may connect to; we can screw up in any of these components, and we should obviously work hard to prevent crashers no matter where. Also notice that this bug was not a pure cloud bug: there was a bug in the client Sync code, i.e. in the browser; but this bug was only activated when the Sync servers also misbehaved, so it could be prevented with a server-only fix/workaround. Still it doesn't count as a real "cloud crash", not any more than an HTML renderer crash that only happens if some website sends corrupt content.