android: Don't keep GSA alive if it supports account change broadcasts.

android: Don't keep GSA alive if it supports account change broadcasts.

Chrome currently connects to a bound service exposed by GSA to get
account change notifications. This elevates GSA's priority for the
system to the foreground level when Chrome is in the foreground,
artificially increasing Chrome's memory footprint. On some phones, the
memory consumption of the GSA process can be above 100MB (PSS), even
though only the account change notifications are required.

Newer versions of GSA send a broadcast intent when the account
changes. This CL listens to the broadcasts, and disonnects from the GSA
service when GSA support the account change broadcast mechanism, freing
the memory for Chrome or other apps on the system.

Note that Chrome still briefly connects to GSA on startup to confirm
that it supports the broadcast. A forthcoming will remove this.

BUG=614388
Review-Url: https://codereview.chromium.org/2431223004
Cr-Commit-Position: refs/heads/master@{#427840}
(cherry picked from commit e1d19b388fc67f31372a4c2df33e20c0c18dfd97)

Committed: https://chromium.googlesource.com/chromium/src/+/0d49cd8de23891fc2d4d4260271795c4c294bcd4

[Benoit L, 2016-11-14 14:57:09]

Description was changed from

==========
android: Don't keep GSA alive if it supports account change broadcasts.

Chrome currently connects to a bound service exposed by GSA to get
account change notifications. This elevates GSA's priority for the
system to the foreground level when Chrome is in the foreground,
artificially increasing Chrome's memory footprint. On some phones, the
memory consumption of the GSA process can be above 100MB (PSS), even
though only the account change notifications are required.

Newer versions of GSA send a broadcast intent when the account
changes. This CL listens to the broadcasts, and disonnects from the GSA
service when GSA support the account change broadcast mechanism, freing
the memory for Chrome or other apps on the system.

Note that Chrome still briefly connects to GSA on startup to confirm
that it supports the broadcast. A forthcoming will remove this.

BUG=614388

Review-Url: https://codereview.chromium.org/2431223004
Cr-Commit-Position: refs/heads/master@{#427840}
(cherry picked from commit e1d19b388fc67f31372a4c2df33e20c0c18dfd97)
==========

to

==========
android: Don't keep GSA alive if it supports account change broadcasts.

Chrome currently connects to a bound service exposed by GSA to get
account change notifications. This elevates GSA's priority for the
system to the foreground level when Chrome is in the foreground,
artificially increasing Chrome's memory footprint. On some phones, the
memory consumption of the GSA process can be above 100MB (PSS), even
though only the account change notifications are required.

Newer versions of GSA send a broadcast intent when the account
changes. This CL listens to the broadcasts, and disonnects from the GSA
service when GSA support the account change broadcast mechanism, freing
the memory for Chrome or other apps on the system.

Note that Chrome still briefly connects to GSA on startup to confirm
that it supports the broadcast. A forthcoming will remove this.

BUG=614388

Review-Url: https://codereview.chromium.org/2431223004
Cr-Commit-Position: refs/heads/master@{#427840}
(cherry picked from commit e1d19b388fc67f31372a4c2df33e20c0c18dfd97)

Committed:
https://chromium.googlesource.com/chromium/src/+/0d49cd8de23891fc2d4d42602717...
==========

[Benoit L, 2016-11-14 14:57:11]

Committed patchset #1 (id:1) manually as
0d49cd8de23891fc2d4d4260271795c4c294bcd4 (tree was closed).

[amineer, 2016-11-15 20:11:59]

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

The reason for reverting is: Causing crashes, see crbug/665396.