| commit | 399b98c7516992ad1c718c0932e1608e609b8b64 | |
| author | dfalcantara <dfalcantara@chromium.org> | |
| Thu, 6 Aug 2015 01:32:01 +0000 (5 18:32 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 6 Aug 2015 01:32:35 +0000 (6 01:32 +0000) | ||
| tree | 658ccacf9f1e75cd9e9c02a75fa2c3c2208cd505 | treesnapshot (tar.gz zip) |
| parent | 8fe412f0caf272435d1d68f531fdb8088225255e | commitdiff |
Restart Chrome by killing it with an out-of-process Activity.
As of KK, Android's AlarmManager has a minimum of 5 seconds before
an alarm may be fired, which means that restarting Chrome via an alarm
takes an inordinate amount of time. Switch to using an Activity
that runs in a separate process and:
1) Kills the main Chrome process
2) Fires an Intent to restart the main Chrome Activity
3) Immediately kills its own process.
BUG=519519
Review URL: https://codereview.chromium.org/1276703002
Cr-Commit-Position: refs/heads/master@{#342042}
As of KK, Android's AlarmManager has a minimum of 5 seconds before
an alarm may be fired, which means that restarting Chrome via an alarm
takes an inordinate amount of time. Switch to using an Activity
that runs in a separate process and:
1) Kills the main Chrome process
2) Fires an Intent to restart the main Chrome Activity
3) Immediately kills its own process.
BUG=519519
Review URL: https://codereview.chromium.org/1276703002
Cr-Commit-Position: refs/heads/master@{#342042}