memory coordinator: Call PurgeMemory() after Notify(SUSPENDED)

memory coordinator: Call PurgeMemory() after Notify(SUSPENDED)

Currently we tentatively call PurgeMemory() before Notify(SUSPENDED).
The order should be reversed as there could be cache allocations before
suspending (throttling) task is actually done, as Eric mentioned[1].

[1] https://codereview.chromium.org/2664703002/#msg15

BUG=684287
Review-Url: https://codereview.chromium.org/2685933003
Cr-Commit-Position: refs/heads/master@{#449189}
Committed: https://chromium.googlesource.com/chromium/src/+/a8c0d87fb51b053a25e3cebfde5ccbd94a24f10c

[bashi, 2017-02-09 01:01:15]

The CQ bit was checked by bashi@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-09 01:02:14]

Dry run: 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, 2017-02-09 01:56:20]

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

[commit-bot: I haz the power, 2017-02-09 01:56:21]

Dry run: This issue passed the CQ dry run.

[bashi, 2017-02-09 01:59:26]

bashi@chromium.org changed reviewers:
+ haraken@chromium.org, tasak@google.com

[bashi, 2017-02-09 01:59:27]

PTAL

I'll remove Notify() call after https://codereview.chromium.org/2664703002/ is
landed anyway, so this might not be necessary...

[haraken, 2017-02-09 02:02:48]

LGTM

[bashi, 2017-02-09 02:04:05]

The CQ bit was checked by bashi@chromium.org

[commit-bot: I haz the power, 2017-02-09 02:04:39]

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, 2017-02-09 02:11:27]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1486605845035640, "parent_rev":
"65a71665fd253d5ca72f71dc9cd1afe344434f84", "commit_rev":
"a8c0d87fb51b053a25e3cebfde5ccbd94a24f10c"}

[commit-bot: I haz the power, 2017-02-09 02:12:02]

Description was changed from

==========
memory coordinator: Call PurgeMemory() after Notify(SUSPENDED)

Currently we tentatively call PurgeMemory() before Notify(SUSPENDED).
The order should be reversed as there could be cache allocations before
suspending (throttling) task is actually done, as Eric mentioned[1].

[1] https://codereview.chromium.org/2664703002/#msg15

BUG=684287
==========

to

==========
memory coordinator: Call PurgeMemory() after Notify(SUSPENDED)

Currently we tentatively call PurgeMemory() before Notify(SUSPENDED).
The order should be reversed as there could be cache allocations before
suspending (throttling) task is actually done, as Eric mentioned[1].

[1] https://codereview.chromium.org/2664703002/#msg15

BUG=684287

Review-Url: https://codereview.chromium.org/2685933003
Cr-Commit-Position: refs/heads/master@{#449189}
Committed:
https://chromium.googlesource.com/chromium/src/+/a8c0d87fb51b053a25e3cebfde5c...
==========

[commit-bot: I haz the power, 2017-02-09 02:12:03]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/a8c0d87fb51b053a25e3cebfde5c...