Revert "Fix sandbox::PolicyBase leak"

Revert "Fix sandbox::PolicyBase leak"

This reverts commit b6a4ff86c730756a73d63cc882ef818fb7818a53
because it breaks Chrome when running as a published app on
Windows Terminal Services or Citrix XenApp.

Original issue's description:
> Fix sandbox::PolicyBase leak
>
> StartSandboxedProcess was missing a Release call, so this was always
> leaking. Use scoped_refptr instead to fix that and prevent it from
> happening in the future.
> TBR=piman@chromium.org
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
>
> Committed: https://crrev.com/b6a4ff86c730756a73d63cc882ef818fb7818a53
> Cr-Commit-Position: refs/heads/master@{#417313}

BUG=659026
TBR=wfh@chromium.org,cpu@chromium.org,jbauman@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

Review-Url: https://codereview.chromium.org/2456573002
Cr-Commit-Position: refs/heads/master@{#427808}
(cherry picked from commit 2bfe4d60b683f05eb7fcb96f9a65d8279923f13f)

Committed: https://chromium.googlesource.com/chromium/src/+/94ee730b26ee227a4696b0f28d958f2a8fd43e5b

[pastarmovj, 2016-10-26 21:52:14]

Description was changed from

==========
Revert "Fix sandbox::PolicyBase leak"

This reverts commit b6a4ff86c730756a73d63cc882ef818fb7818a53
because it breaks Chrome when running as a published app on
Windows Terminal Services or Citrix XenApp.

Original issue's description:
> Fix sandbox::PolicyBase leak
>
> StartSandboxedProcess was missing a Release call, so this was always
> leaking. Use scoped_refptr instead to fix that and prevent it from
> happening in the future.
> TBR=piman@chromium.org
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
>
> Committed: https://crrev.com/b6a4ff86c730756a73d63cc882ef818fb7818a53
> Cr-Commit-Position: refs/heads/master@{#417313}

BUG=659026
TBR=wfh@chromium.org,cpu@chromium.org,jbauman@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

Review-Url: https://codereview.chromium.org/2456573002
Cr-Commit-Position: refs/heads/master@{#427808}
(cherry picked from commit 2bfe4d60b683f05eb7fcb96f9a65d8279923f13f)
==========

to

==========
Revert "Fix sandbox::PolicyBase leak"

This reverts commit b6a4ff86c730756a73d63cc882ef818fb7818a53
because it breaks Chrome when running as a published app on
Windows Terminal Services or Citrix XenApp.

Original issue's description:
> Fix sandbox::PolicyBase leak
>
> StartSandboxedProcess was missing a Release call, so this was always
> leaking. Use scoped_refptr instead to fix that and prevent it from
> happening in the future.
> TBR=piman@chromium.org
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
>
> Committed: https://crrev.com/b6a4ff86c730756a73d63cc882ef818fb7818a53
> Cr-Commit-Position: refs/heads/master@{#417313}

BUG=659026
TBR=wfh@chromium.org,cpu@chromium.org,jbauman@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

Review-Url: https://codereview.chromium.org/2456573002
Cr-Commit-Position: refs/heads/master@{#427808}
(cherry picked from commit 2bfe4d60b683f05eb7fcb96f9a65d8279923f13f)

Committed:
https://chromium.googlesource.com/chromium/src/+/94ee730b26ee227a4696b0f28d95...
==========

[pastarmovj, 2016-10-26 21:52:15]

Committed patchset #1 (id:1) manually as
94ee730b26ee227a4696b0f28d958f2a8fd43e5b.

[Will Harris, 2016-10-26 21:54:13]

On 2016/10/26 21:52:15, pastarmovj wrote:
> Committed patchset #1 (id:1) manually as
> 94ee730b26ee227a4696b0f28d958f2a8fd43e5b.

wow that was merged really quickly - we did not want to do a bake on Canary?

[pastarmovj, 2016-10-26 22:00:32]

On 2016/10/26 21:54:13, Will Harris wrote:
> On 2016/10/26 21:52:15, pastarmovj wrote:
> > Committed patchset #1 (id:1) manually as
> > 94ee730b26ee227a4696b0f28d958f2a8fd43e5b.
> 
> wow that was merged really quickly - we did not want to do a bake on Canary?

Desperate times - desperate measures :) 

Joke aside, I think since it is 99% clean revert and this CL seems to be a
singleton I think it makes sense to verify it as quickly as possible on the
affected branch to avoid noise from future changes that might skew tests.