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.ch

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.