[Mac] Only enable the CFBundleBlocker in the browser process.

[Mac] Only enable the CFBundleBlocker in the browser process.

In child processes, which are sandboxed in most cases, the sandbox will prevent
access to the filesystem locations where the potentially blocked bundles are
stored. Furthermore, on macOS 10.11 and higher, the Google Chrome build is
codesigned in such a way where bundle loading is blocked by SIP.

This reduces some of the "triggered DYLD shared region unnest for map" messages.

BUG=428858
R=mark@chromium.org

Committed: https://crrev.com/65e732d3b4dc595512b731143fd49d372acc1a87
Cr-Commit-Position: refs/heads/master@{#409244}

[Robert Sesek, 2016-08-02 14:43:03]

The CQ bit was checked by rsesek@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-02 14:43:20]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-02 15:19:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-02 15:19:08]

Dry run: This issue passed the CQ dry run.

[Mark Mentovai, 2016-08-02 15:45:25]

LGTM

[Robert Sesek, 2016-08-02 18:02:53]

rsesek@chromium.org changed reviewers:
+ thakis@chromium.org

[Robert Sesek, 2016-08-02 18:02:53]

+thakis for //chrome OWNERS

[Nico, 2016-08-02 18:06:25]

value-adding lgtm

[Robert Sesek, 2016-08-02 18:06:55]

The CQ bit was checked by rsesek@chromium.org

[commit-bot: I haz the power, 2016-08-02 18:07:31]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-02 18:13:38]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-02 18:15:54]

Description was changed from

==========
[Mac] Only enable the CFBundleBlocker in the browser process.

In child processes, which are sandboxed in most cases, the sandbox will prevent
access to the filesystem locations where the potentially blocked bundles are
stored. Furthermore, on macOS 10.11 and higher, the Google Chrome build is
codesigned in such a way where bundle loading is blocked by SIP.

This reduces some of the "triggered DYLD shared region unnest for map" messages.

BUG=428858
R=mark@chromium.org
==========

to

==========
[Mac] Only enable the CFBundleBlocker in the browser process.

In child processes, which are sandboxed in most cases, the sandbox will prevent
access to the filesystem locations where the potentially blocked bundles are
stored. Furthermore, on macOS 10.11 and higher, the Google Chrome build is
codesigned in such a way where bundle loading is blocked by SIP.

This reduces some of the "triggered DYLD shared region unnest for map" messages.

BUG=428858
R=mark@chromium.org

Committed: https://crrev.com/65e732d3b4dc595512b731143fd49d372acc1a87
Cr-Commit-Position: refs/heads/master@{#409244}
==========

[commit-bot: I haz the power, 2016-08-02 18:15:55]

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

[Robert Sesek, 2016-08-05 17:30:56]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2218163002/ by rsesek@chromium.org.

The reason for reverting is: Speculative revert for perf regression.

BUG=https://crbug.com/634917.