diff options
author | kuchhal@chromium.org <kuchhal@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-05 22:31:03 +0000 |
---|---|---|
committer | kuchhal@chromium.org <kuchhal@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-11-05 22:31:03 +0000 |
commit | 157d547807a2b9d0e42f17636ffc39336a9a62f6 (patch) | |
tree | 9ae45f8dcd0a5298b39c44dd94d07219200e73c1 /printing | |
parent | 23ffe4da52705ce6fd12d3aa3e178c2b5dd79598 (diff) | |
download | chromium_src-157d547807a2b9d0e42f17636ffc39336a9a62f6.zip chromium_src-157d547807a2b9d0e42f17636ffc39336a9a62f6.tar.gz chromium_src-157d547807a2b9d0e42f17636ffc39336a9a62f6.tar.bz2 |
Change id that identifies client in crash reports. Whenever metrics service recording is enabled, it sets the client id for crash reporting.
- On Windows this id gets stored in the registry so that we can read it pretty early regardless of the process type. If the id has not been generated (like in the case of first run) we initialize with empty string but the real id gets inserted once metrics service gets initialized.
- On Linux we were creating a hash and storing it in 'Consent to Send Stats'. This change replaces that hash with the metrics id. Unlike before calling SetConsentToSendStats doesn't generate a new id, if an id already exists.
- On Mac there was no id set. Now we use metrics id as guid for the browser process. For other process types a change is still required to pass that id as command line param to renderers/plugins (like Linux).
BUG=23658
TEST=Cause a deliberate crash in Chrome renderer/browser/plugin and make sure the clientID reported to the crash server is the right GUID.
Review URL: http://codereview.chromium.org/346007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@31143 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'printing')
0 files changed, 0 insertions, 0 deletions