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

Revert of android: Don't keep GSA alive if it supports account change broadcasts. (patchset #1 id:1 of https://codereview.chromium.org/2497313002/ )

Reason for revert:
Causing crashes, see crbug/665396

Original issue's description:
> 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

TBR=lizeb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=614388
NOTRY=true
NOPRESUBMIT=true

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

The CQ bit was checked by amineer@chromium.org

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

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

[commit-bot: I haz the power, 2016-11-15 20:12:35]

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-11-15 20:12:36]

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

[commit-bot: I haz the power, 2016-11-15 20:12:38]

CLs for remote refs other than refs/pending/heads/master must contain NOTRY=true
and NOPRESUBMIT=true in order for the CQ to process them

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

Description was changed from

==========
Revert of android: Don't keep GSA alive if it supports account change
broadcasts. (patchset #1 id:1 of https://codereview.chromium.org/2497313002/ )

Reason for revert:
Causing crashes, see crbug/665396

Original issue's description:
> 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...

TBR=lizeb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=614388
==========

to

==========
Revert of android: Don't keep GSA alive if it supports account change
broadcasts. (patchset #1 id:1 of https://codereview.chromium.org/2497313002/ )

Reason for revert:
Causing crashes, see crbug/665396

Original issue's description:
> 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...

TBR=lizeb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=614388
NOTRY=true
NOPRESUBMIT=true
==========

[amineer, 2016-11-15 20:13:17]

The CQ bit was checked by amineer@chromium.org

[commit-bot: I haz the power, 2016-11-15 20:13:43]

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-11-15 20:38:43]

Description was changed from

==========
Revert of android: Don't keep GSA alive if it supports account change
broadcasts. (patchset #1 id:1 of https://codereview.chromium.org/2497313002/ )

Reason for revert:
Causing crashes, see crbug/665396

Original issue's description:
> 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...

TBR=lizeb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=614388
NOTRY=true
NOPRESUBMIT=true
==========

to

==========
Revert of android: Don't keep GSA alive if it supports account change
broadcasts. (patchset #1 id:1 of https://codereview.chromium.org/2497313002/ )

Reason for revert:
Causing crashes, see crbug/665396

Original issue's description:
> 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...

TBR=lizeb@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=614388
NOTRY=true
NOPRESUBMIT=true
==========

[commit-bot: I haz the power, 2016-11-15 20:38:44]

Committed patchset #1 (id:1)