Unconditionally send Chrome and Chrome Frame events through ETW machinery.

Unconditionally send Chrome and Chrome Frame events through ETW machinery.

Previously, these components only registered themselves if CHROME_ETW_LOGGING was set in the environment.  This is likely preventing the new log machinery in http://crrev.com/126240 from providing useful information on the main waterfall bots.

Siggi: overall
Brett: chrome/common

BUG=none
TEST=none
R=siggi@chromium.org,brettw@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=126810

[Sigurður Ásgeirsson, 2012-03-14 14:43:47]

lgtm, thanks!

The reason the environment snooping was added in the first place was a small
perf regression on the XP perfbots. If that recurs, then worst case I'd say to
reinstate the env check for Chrome only under XP?

[brettw, 2012-03-14 16:05:40]

LGTM, I don't really have an opinion on this

[commit-bot: I haz the power, 2012-03-14 18:44:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/grt@chromium.org/9702021/1

[commit-bot: I haz the power, 2012-03-14 21:55:03]

Try job failure for 9702021-1 (retry) on win_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-14 22:28:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/grt@chromium.org/9702021/1

[commit-bot: I haz the power, 2012-03-15 00:13:19]

Try job failure for 9702021-1 (retry) (retry) on linux_rel for step "update".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

Step "update" is always a major failure.
Look at the try server FAQ for more details.