diff options
| author | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-15 18:24:24 +0000 |
|---|---|---|
| committer | jar@chromium.org <jar@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-12-15 18:24:24 +0000 |
| commit | 51f14a3192290c9c4cfb6c9bad953e9ad1102f48 (patch) | |
| tree | 4cb3971fa645b7aaefde6f38a0038ae516653286 /base | |
| parent | 1a88f223ef4d02e0d66e7ee505539d9ba275e968 (diff) | |
| download | chromium_src-51f14a3192290c9c4cfb6c9bad953e9ad1102f48.zip chromium_src-51f14a3192290c9c4cfb6c9bad953e9ad1102f48.tar.gz chromium_src-51f14a3192290c9c4cfb6c9bad953e9ad1102f48.tar.bz2 | |
Deserialize UMA flag on histograms moving from renderer to browsers
During a recent migration, we forgot to properly resurrect the
flags in a histogram as they are carried from the renderer processes
into the browser process. Since the flag is the critical marker that
identifies which histograms to upload via UMA, this caused renderer
histograms to not get reported.
BUG=30478
r=raman.tenetti,mbelshe
Review URL: http://codereview.chromium.org/505006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34574 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base')
| -rw-r--r-- | base/histogram.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/base/histogram.cc b/base/histogram.cc index 3a5a5b2..b421156d 100644 --- a/base/histogram.cc +++ b/base/histogram.cc @@ -464,6 +464,7 @@ bool Histogram::DeserializeHistogramInfo(const std::string& histogram_info) { histogram_name; } else { render_histogram->AddSampleSet(sample); + render_histogram->SetFlags(flags & ~kIPCSerializationSourceFlag); } return true; |