Have a Page's MemoryPurgeController be a separate allocation also.

Have a Page's MemoryPurgeController be a separate allocation also.

A Page keeps and owns a number of controllers, each being separately allocated.
Extend that to also apply to MemoryPurgeController; it is created on demand,
and no longer a part object.

R=haraken
BUG=520496
Committed: https://crrev.com/c6dad2677039627a2ddc5666182565d82201163e
git-svn-id: svn://svn.chromium.org/blink/trunk@202261 bbb929c8-8fbe-4397-9dbb-9b2b20218538

[sof, 2015-09-15 06:17:02]

sigbjornf@opera.com changed reviewers:
+ bashi@chromium.org, haraken@chromium.org

[sof, 2015-09-15 06:17:03]

please take a look.

not much in this one, but I think it is slightly preferable to have this
representation for MemoryPurgeController.

[haraken, 2015-09-15 06:20:41]

LGTM

[sof, 2015-09-15 06:43:08]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2015-09-15 06:43:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1335373003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1335373003/1

[commit-bot: I haz the power, 2015-09-15 07:15:45]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=202261

[commit-bot: I haz the power, 2015-09-23 12:43:08]

Patchset 1 (id:??) landed as
https://crrev.com/c6dad2677039627a2ddc5666182565d82201163e