4 ms·

The actual reason for the crash is explained in the bug report http://code.google.com/p/chromium/issues/detail?id=165171#c27 http://code.google.com/p/chromium/i

by VMG 14y ago

The actual reason for the crash is explained in the bug report http://code.google.com/p/chromium/issues/detail?id=165171#c27 http://code.google.com/p/chromium/issues/detail?id=165171#c2... Renaming this bug as it really has nothing to do with GMail specifically. To clarify: - Chrome Sync Server relies on a backend infrastructure component to enforce quotas on per-datatype sync traffic. - That quota service experienced traffic problems today due to a faulty load balancing configuration change. - That change was to a core piece of infrastructure that many services at Google depend on. This means other services may have been affected at the same time, leading to the confounding original title of this bug. - Because of the quota service failure, Chrome Sync Servers reacted too conservatively by telling clients to throttle "all" data types, without accounting for the fact that not all client versions support all data types. The crash is due to faulty logic responsible for handling "throttled" data types on the client when the data types are unrecognized.

irahul 14y ago
Looking at the code changes, the headline is just fear mongering. The main change is a check for the datatype; it wasn't checking for it earlier: http://src.chromium.org/viewvc/chrome/trunk/src/sync/engine/syncer_proto_util.cc?r1=172232&r2=172231&pathrev=172232 http://src.chromium.org/viewvc/chrome/trunk/src/sync/engine/... It was a simple logic bug. From the crash traces, it was an out of bound exception: terminate called after throwing an instance of 'std::out_of_range But I don't think reporters are going to take the time to talk to someone who can analyze it and give them an accurate picture, even though chromium is open source and issues are discussed and fixed publically.
alanctgardner2 14y ago
The headline is definitely ridiculous link bait. Google doesn't have some big red button somewhere to nuke Chrome browsers. There was a bug which only appeared when there was an unexpected server behaviour. That said, it was bizarre for a bit that Chrome was crashing because Google was down. I was actually considering switching off Chrome until I learned it was only an issue with Sync. Fortunately, Google doesn't make the Sync service mandatory, unlike some game ( and mouse ) manufacturers.

by VMG 14y ago

irahul 14y ago

Looking at the code changes, the headline is just fear mongering. The main change is a check for the datatype; it wasn't checking for it earlier: http://src.chromium.org/viewvc/chrome/trunk/src/sync/engine/syncer_proto_util.cc?r1=172232&r2=172231&pathrev=172232 http://src.chromium.org/viewvc/chrome/trunk/src/sync/engine/... It was a simple logic bug. From the crash traces, it was an out of bound exception: terminate called after throwing an instance of 'std::out_of_range But I don't think reporters are going to take the time to talk to someone who can analyze it and give them an accurate picture, even though chromium is open source and issues are discussed and fixed publically.

alanctgardner2 14y ago

The headline is definitely ridiculous link bait. Google doesn't have some big red button somewhere to nuke Chrome browsers. There was a bug which only appeared when there was an unexpected server behaviour. That said, it was bizarre for a bit that Chrome was crashing because Google was down. I was actually considering switching off Chrome until I learned it was only an issue with Sync. Fortunately, Google doesn't make the Sync service mandatory, unlike some game ( and mouse ) manufacturers.