Enable AreCrossProcessFramesPossible on Android

Enable AreCrossProcessFramesPossible on Android

Previous attempts to enable cross process frames on Android have caused
changes in memory usage on Android Webview tests, resulting in them
being reverted. This might be because the flag changed the behavior of
--single-process, which is no longer the case since r485292 landed.

The regressed benchmark was memory.top_10_mobile under Android Webview
tests. We expect that the problem is now fixed and we can land this
without causing regressions, but this is still a speculative attempt.

BUG=690229, 737264
Review-Url: https://codereview.chromium.org/2965523002
Cr-Commit-Position: refs/heads/master@{#485361}
Committed: https://chromium.googlesource.com/chromium/src/+/c3de9c1ad085f8a2210eb290b719468be08323c3

[kenrb, 2017-07-10 18:06:44]

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

[commit-bot: I haz the power, 2017-07-10 18:06:53]

Dry run: CQ is trying da patch.

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

[kenrb, 2017-07-10 18:08:08]

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

[commit-bot: I haz the power, 2017-07-10 18:08:20]

Dry run: CQ is trying da patch.

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

[kenrb, 2017-07-10 18:59:46]

Description was changed from

==========
[WIP] Re-enable AreCrossProcessFramesPossible on Android

Currently just trying to reproduce and narrow down perf regressions.

BUG=690229, 737264
==========

to

==========
Enable AreCrossProcessFramesPossible on Android

Previous attempts to enable cross process frames on Android have caused
changes in memory usage on Android Webview tests, resulting in them
being reverted. This might be because the flag changed the behavior of
--single-process, which is no longer the case since r485292 landed.

The regressed benchmark was memory.top_10_mobile under Android Webview
tests. We expect that the problem is now fixed and we can land this
without causing regressions, but this is still a speculative attempt.

BUG=690229, 737264
==========

[commit-bot: I haz the power, 2017-07-10 19:40:41]

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

[commit-bot: I haz the power, 2017-07-10 19:40:42]

Dry run: This issue passed the CQ dry run.

[kenrb, 2017-07-10 19:42:25]

kenrb@chromium.org changed reviewers:
+ creis@chromium.org

[kenrb, 2017-07-10 19:42:26]

creis@: PTAL?

[Charlie Reis, 2017-07-10 19:48:00]

LGTM!

[kenrb, 2017-07-10 20:08:18]

The CQ bit was checked by kenrb@chromium.org

[commit-bot: I haz the power, 2017-07-10 20:08:41]

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, 2017-07-10 20:17:42]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1499717298757200,
"parent_rev": "912335bc3e0cf9a880286811d0f342c3a7f1c230", "commit_rev":
"c3de9c1ad085f8a2210eb290b719468be08323c3"}

[commit-bot: I haz the power, 2017-07-10 20:17:56]

Description was changed from

==========
Enable AreCrossProcessFramesPossible on Android

Previous attempts to enable cross process frames on Android have caused
changes in memory usage on Android Webview tests, resulting in them
being reverted. This might be because the flag changed the behavior of
--single-process, which is no longer the case since r485292 landed.

The regressed benchmark was memory.top_10_mobile under Android Webview
tests. We expect that the problem is now fixed and we can land this
without causing regressions, but this is still a speculative attempt.

BUG=690229, 737264
==========

to

==========
Enable AreCrossProcessFramesPossible on Android

Previous attempts to enable cross process frames on Android have caused
changes in memory usage on Android Webview tests, resulting in them
being reverted. This might be because the flag changed the behavior of
--single-process, which is no longer the case since r485292 landed.

The regressed benchmark was memory.top_10_mobile under Android Webview
tests. We expect that the problem is now fixed and we can land this
without causing regressions, but this is still a speculative attempt.

BUG=690229, 737264

Review-Url: https://codereview.chromium.org/2965523002
Cr-Commit-Position: refs/heads/master@{#485361}
Committed:
https://chromium.googlesource.com/chromium/src/+/c3de9c1ad085f8a2210eb290b719...
==========

[commit-bot: I haz the power, 2017-07-10 20:17:58]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/c3de9c1ad085f8a2210eb290b719...