Catch failed attempts to set Omaha alarms
commitf0eaf2afd76b3502b898091ed82c1af391c73cf4
authordfalcantara <dfalcantara@chromium.org>
Tue, 18 Aug 2015 00:50:11 +0000 (17 17:50 -0700)
committerCommit bot <commit-bot@chromium.org>
Tue, 18 Aug 2015 00:50:43 +0000 (18 00:50 +0000)
treeda412f918d8a387cae49e1e8542561d09febcc0f
parent5b2968405fff04316a66217dc081a8bbd9a18597
Catch failed attempts to set Omaha alarms

Catch the SecurityExceptions that get thrown when Chrome
has 500 alarms registered.  A proper fix is still being researched
because even though there is a slow leak of alarms in the Omaha code,
we share the 500 alarm limit with other components.

BUG=483695

Review URL: https://codereview.chromium.org/1299793003

Cr-Commit-Position: refs/heads/master@{#343786}
chrome/android/java/src/org/chromium/chrome/browser/omaha/ExponentialBackoffScheduler.java
chrome/android/java/src/org/chromium/chrome/browser/omaha/OmahaClient.java