Revert of android: Randomize initial child service bind order

Revert of android: Randomize initial child service bind order (patchset #3 id:40001 of https://codereview.chromium.org/2557273004/ )

Reason for revert:
Android keeps the intent for a long time, so
randomize doesn't help at all. More details:
crbug.com/664341#c91

Original issue's description:
> android: Randomize initial child service bind order
>
> Android restarts crashed services with the previous intent.
> If browser crashes and is restarted at the same time, then
> it's possible to bind to the restarted service with stale
> intent and bundle data. See crbug.com/664341#c83 for an
> example. Randomizing the start up order is a pure
> workaround to make this case less likely.
>
> BUG=664341
>
> Committed: https://crrev.com/bb725fed9bd8c672178c8a815f4b1a2500eef444
> Cr-Commit-Position: refs/heads/master@{#437367}

TBR=agrieve@chromium.org,jcivelli@chromium.org,mariakhomenko@chromium.org,hanxi@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=664341
Committed: https://crrev.com/2e30a3dfda9367264173c8707bbc22d7530f7a77
Cr-Commit-Position: refs/heads/master@{#438042}

[boliu, 2016-12-13 03:00:27]

The CQ bit was checked by boliu@chromium.org

[boliu, 2016-12-13 03:00:28]

Created Revert of android: Randomize initial child service bind order

[commit-bot: I haz the power, 2016-12-13 03:01:22]

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-12-13 03:49:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1481598027706990, "parent_rev":
"7fc19569f49b3f383e7f983ad880bccc590a19b6", "commit_rev":
"363e41ace14ed25379a266444c9e9212ae1be4fc"}

[commit-bot: I haz the power, 2016-12-13 03:49:30]

Description was changed from

==========
Revert of android: Randomize initial child service bind order (patchset #3
id:40001 of https://codereview.chromium.org/2557273004/ )

Reason for revert:
Android keeps the intent for a long time, so
randomize doesn't help at all. More details:
crbug.com/664341#c91

Original issue's description:
> android: Randomize initial child service bind order
> 
> Android restarts crashed services with the previous intent.
> If browser crashes and is restarted at the same time, then
> it's possible to bind to the restarted service with stale
> intent and bundle data. See crbug.com/664341#c83 for an
> example. Randomizing the start up order is a pure
> workaround to make this case less likely.
> 
> BUG=664341
> 
> Committed: https://crrev.com/bb725fed9bd8c672178c8a815f4b1a2500eef444
> Cr-Commit-Position: refs/heads/master@{#437367}

TBR=agrieve@chromium.org,jcivelli@chromium.org,mariakhomenko@chromium.org,han...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=664341
==========

to

==========
Revert of android: Randomize initial child service bind order (patchset #3
id:40001 of https://codereview.chromium.org/2557273004/ )

Reason for revert:
Android keeps the intent for a long time, so
randomize doesn't help at all. More details:
crbug.com/664341#c91

Original issue's description:
> android: Randomize initial child service bind order
> 
> Android restarts crashed services with the previous intent.
> If browser crashes and is restarted at the same time, then
> it's possible to bind to the restarted service with stale
> intent and bundle data. See crbug.com/664341#c83 for an
> example. Randomizing the start up order is a pure
> workaround to make this case less likely.
> 
> BUG=664341
> 
> Committed: https://crrev.com/bb725fed9bd8c672178c8a815f4b1a2500eef444
> Cr-Commit-Position: refs/heads/master@{#437367}

TBR=agrieve@chromium.org,jcivelli@chromium.org,mariakhomenko@chromium.org,han...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=664341

Review-Url: https://codereview.chromium.org/2571723002
==========

[commit-bot: I haz the power, 2016-12-13 03:49:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-13 03:52:05]

Description was changed from

==========
Revert of android: Randomize initial child service bind order (patchset #3
id:40001 of https://codereview.chromium.org/2557273004/ )

Reason for revert:
Android keeps the intent for a long time, so
randomize doesn't help at all. More details:
crbug.com/664341#c91

Original issue's description:
> android: Randomize initial child service bind order
> 
> Android restarts crashed services with the previous intent.
> If browser crashes and is restarted at the same time, then
> it's possible to bind to the restarted service with stale
> intent and bundle data. See crbug.com/664341#c83 for an
> example. Randomizing the start up order is a pure
> workaround to make this case less likely.
> 
> BUG=664341
> 
> Committed: https://crrev.com/bb725fed9bd8c672178c8a815f4b1a2500eef444
> Cr-Commit-Position: refs/heads/master@{#437367}

TBR=agrieve@chromium.org,jcivelli@chromium.org,mariakhomenko@chromium.org,han...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=664341

Review-Url: https://codereview.chromium.org/2571723002
==========

to

==========
Revert of android: Randomize initial child service bind order (patchset #3
id:40001 of https://codereview.chromium.org/2557273004/ )

Reason for revert:
Android keeps the intent for a long time, so
randomize doesn't help at all. More details:
crbug.com/664341#c91

Original issue's description:
> android: Randomize initial child service bind order
>
> Android restarts crashed services with the previous intent.
> If browser crashes and is restarted at the same time, then
> it's possible to bind to the restarted service with stale
> intent and bundle data. See crbug.com/664341#c83 for an
> example. Randomizing the start up order is a pure
> workaround to make this case less likely.
>
> BUG=664341
>
> Committed: https://crrev.com/bb725fed9bd8c672178c8a815f4b1a2500eef444
> Cr-Commit-Position: refs/heads/master@{#437367}

TBR=agrieve@chromium.org,jcivelli@chromium.org,mariakhomenko@chromium.org,han...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=664341

Committed: https://crrev.com/2e30a3dfda9367264173c8707bbc22d7530f7a77
Cr-Commit-Position: refs/heads/master@{#438042}
==========

[commit-bot: I haz the power, 2016-12-13 03:52:05]

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