Merge M43: Enable appcontainer on M43

Merge M43: Enable appcontainer on M43

Reverted appcontainer mini-dump creation. As we would have received sufficient crash reports for analysis, reverting.

BUG=468922, 473715, 455496
R=cpu@chromium.org, jschuh@chromium.org, cpu, wfh

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

Cr-Commit-Position: refs/heads/master@{#324566}
(cherry picked from commit 55c2f2365e41a170f37ed56d13ced4ef054abffa)

Adding minidump creation when launching renderer process fails in appcontainer mode. Also reenabled appcontainer for renderer and fixed policy use after free case.

BUG=468922, 473715, 455496
Review URL: https://codereview.chromium.org/1058373003

Cr-Commit-Position: refs/heads/master@{#324348}
(cherry picked from commit 9203ef8157d4d47970dd0255d7de009697618bb2)

Committed: https://chromium.googlesource.com/chromium/src/+/638956dafee998e7fd761afdd052959b01ad3bc7

[laforge, 2015-05-21 19:59:24]

laforge@google.com changed reviewers:
+ laforge@google.com

[laforge, 2015-05-21 19:59:25]

lgtm

[cpu_(ooo_6.6-7.5), 2015-05-21 20:43:56]

cpu@chromium.org changed reviewers:
+ laforge@chromium.org
- laforge@google.com

[cpu_(ooo_6.6-7.5), 2015-05-21 20:43:56]

lgtm

[cpu_(ooo_6.6-7.5), 2015-05-21 20:46:23]

don't we need the vs debugger (forshaw) fix?

[Will Harris, 2015-05-21 20:47:35]

On 2015/05/21 20:46:23, cpu wrote:
> don't we need the vs debugger (forshaw) fix?

people debugging Chrome with VS can use --disable-appcontainer as a
workaround...?

[Will Harris, 2015-05-21 21:04:16]

Committed patchset #1 (id:1) manually as
638956dafee998e7fd761afdd052959b01ad3bc7.