Add creation tracking for ActiveVerifier.

Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
Committed: https://crrev.com/1f9673dbd1b71cfa5a0dc5ab06509368153bcb20
Cr-Commit-Position: refs/heads/master@{#379996}

[Will Harris, 2016-03-08 21:19:58]

Patchset #1 (id:1) has been deleted

[Will Harris, 2016-03-08 21:20:18]

Description was changed from

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
==========

to

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
==========

[Will Harris, 2016-03-08 21:20:19]

wfh@chromium.org changed reviewers:
+ scottmg@chromium.org

[Will Harris, 2016-03-08 21:20:25]

PTAL

[scottmg, 2016-03-08 21:25:37]

lgtm

[Will Harris, 2016-03-08 22:40:41]

The CQ bit was checked by wfh@chromium.org

[commit-bot: I haz the power, 2016-03-08 22:41:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1767293005/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1767293005/20001

[commit-bot: I haz the power, 2016-03-09 00:33:12]

Description was changed from

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
==========

to

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
==========

[commit-bot: I haz the power, 2016-03-09 00:33:13]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2016-03-09 00:34:07]

Description was changed from

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753
==========

to

==========
Add creation tracking for ActiveVerifier.

Sometimes the ActiveVerifier gets instantiated inside chrome_child's
copy of base and sometimes inside chrome.exe's copy of base.

The ActiveVerifier should only be running from chrome.exe's copy of base,
but before enforcing this, am adding a check to determine what is causing
this unpredictability.

See bug for the gory details.

BUG=592753

Committed: https://crrev.com/1f9673dbd1b71cfa5a0dc5ab06509368153bcb20
Cr-Commit-Position: refs/heads/master@{#379996}
==========

[commit-bot: I haz the power, 2016-03-09 00:34:08]

Patchset 1 (id:??) landed as
https://crrev.com/1f9673dbd1b71cfa5a0dc5ab06509368153bcb20
Cr-Commit-Position: refs/heads/master@{#379996}