Add a UMA stat to track if the Browser blacklist is Set on the Renderer
commit174213aed78f7bd2c654ab3797dec7485593402d
authorcsharp@chromium.org <csharp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 15 Feb 2014 00:32:30 +0000 (15 00:32 +0000)
committercsharp@chromium.org <csharp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Sat, 15 Feb 2014 00:32:30 +0000 (15 00:32 +0000)
treef72dc17087713e328362977a29cbfa9f294511d2
parente0a4d737b5a2e1efb828e371f905aced30ea7904
Add a UMA stat to track if the Browser blacklist is Set on the Renderer

This shouldn't be happening, but we got some crash reports suggesting it
does. Unable to repo locally so this stat will verify it does occur and
then can be used to verify our fixes actually fix it.

TBR=asvitkine@chromium.org
BUG=329023

Review URL: https://codereview.chromium.org/166953002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251454 0039d316-1c4b-4281-b951-d872f2087c98
12 files changed:
chrome/browser_tests.isolate
chrome/chrome_renderer.gypi
chrome/interactive_ui_tests.isolate
chrome/renderer/DEPS
chrome/renderer/chrome_content_renderer_client.cc
chrome/unit_tests.isolate
chrome_elf/blacklist/blacklist.cc
chrome_elf/blacklist/blacklist.h
chrome_elf/blacklist/test/blacklist_test.cc
chrome_elf/blacklist/test/blacklist_test_main_dll.def
chrome_elf/chrome_elf.def
tools/metrics/histograms/histograms.xml