Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org

Committed: https://crrev.com/cad57047c680feda55633193eba84cb181e6c1b9
Cr-Commit-Position: refs/heads/master@{#377217}

[mnaganov (inactive), 2016-02-23 02:06:13]

mnaganov@chromium.org changed reviewers:
+ yusufo@chromium.org

[mnaganov (inactive), 2016-02-23 02:06:14]

Yusuf, PTAL!

Tested by building a stable channel Chrome and launching Twitter. I'm not sure
how to test the change in ChromePrerenderService, though. I'm not actually sure
how it is supposed to be used.

Note that as the new Android SDK will be released, there will be no need to pass
ChildProcessCreationParams for Chrome, only for Android WebView, and this code
will be refactored.

[Yusuf, 2016-02-23 20:10:13]

I would ignore PrerenderService as it is deprecated. I should delete that when
we have time for cleanup.

lizeb@ FYI.

lgtm but you will need a chrome/android OWNER

[mnaganov (inactive), 2016-02-23 21:31:38]

mnaganov@chromium.org changed reviewers:
+ dtrainor@chromium.org

[mnaganov (inactive), 2016-02-23 21:31:38]

Thanks, Yusuf!

David, you reviewed the original change, this is a small addendum to fix Custom
Tabs.

[mnaganov (inactive), 2016-02-24 02:46:06]

Description was changed from

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
==========

to

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org
==========

[mnaganov (inactive), 2016-02-24 02:46:46]

Dave has provided his approval over IM and suggested TBRing the change to him.
Thanks, Dave!

[mnaganov (inactive), 2016-02-24 02:46:51]

The CQ bit was checked by mnaganov@chromium.org

[commit-bot: I haz the power, 2016-02-24 02:50:21]

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

[commit-bot: I haz the power, 2016-02-24 04:12:39]

Description was changed from

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org
==========

to

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org
==========

[commit-bot: I haz the power, 2016-02-24 04:12:39]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-24 04:13:29]

Description was changed from

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org
==========

to

==========
Pass ChildProcessCreationParams in ChildProcessLauncher.warmUp

This fixes the use case when Chrome is started via Custom Tabs.

BUG=588397
TBR=dtrainor@chromium.org

Committed: https://crrev.com/cad57047c680feda55633193eba84cb181e6c1b9
Cr-Commit-Position: refs/heads/master@{#377217}
==========

[commit-bot: I haz the power, 2016-02-24 04:13:30]

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