Commit History transaction when app is backgrounded on iOS

Commit History transaction when app is backgrounded on iOS

Request time from the OS when the application is backgrounded on iOS to
try to commit all pending history transactions.

BUG=429756
Committed: https://crrev.com/62bd9e3de2849b73f09d618cab31a03e072bcc73
Cr-Commit-Position: refs/heads/master@{#321329}

[sdefresne, 2015-03-18 17:26:46]

sdefresne@chromium.org changed reviewers:
+ droger@chromium.org

[sdefresne, 2015-03-18 17:26:47]

PTAL

[sdefresne, 2015-03-18 17:28:21]

Patchset #1 (id:1) has been deleted

[droger, 2015-03-18 18:07:09]

lgtm

It looks overkill to have both MakeCriticalClosure around the task, and a
ScopedCriticalAction inside the task, but it probably does not hurt either.

[sdefresne, 2015-03-19 08:25:17]

On 2015/03/18 18:07:09, droger wrote:
> lgtm
> 
> It looks overkill to have both MakeCriticalClosure around the task, and a
> ScopedCriticalAction inside the task, but it probably does not hurt either.

HistoryBackend::Commit() is called from other location than the critical closure
(it is called periodically). We also want to complete those commit if they
start, even if they have not been started by the critical closure.

[sdefresne, 2015-03-19 08:25:51]

sky: FYI, this is upstreaming iOS code

[sdefresne, 2015-03-19 08:25:54]

The CQ bit was checked by sdefresne@chromium.org

[commit-bot: I haz the power, 2015-03-19 08:26:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1015153002/20001

[commit-bot: I haz the power, 2015-03-19 10:30:10]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-03-19 10:30:44]

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