Perform full gcs when context disposals happen too frequent.

Perform full gcs when context disposals happen too frequent.

Removed context disposal logic from IdleNotification.

BUG=

[jochen (gone - plz use gerrit), 2014-08-07 09:14:51]

lgtm

https://codereview.chromium.org/449813002/diff/60001/src/heap/heap.cc
File src/heap/heap.cc (right):

https://codereview.chromium.org/449813002/diff/60001/src/heap/heap.cc#newcode...
src/heap/heap.cc:4328: CollectAllGarbage(kReduceMemoryFootprintMask,
this is a somewhat new behavior, because previously we'd only do this if there
was a context disposal notification before, no?

But since we're respecting the idle hint, I think that's ok

[Hannes Payer (out of office), 2014-08-07 10:53:30]

https://codereview.chromium.org/449813002/diff/60001/src/heap/heap.cc
File src/heap/heap.cc (right):

https://codereview.chromium.org/449813002/diff/60001/src/heap/heap.cc#newcode...
src/heap/heap.cc:4328: CollectAllGarbage(kReduceMemoryFootprintMask,
On 2014/08/07 09:14:51, jochen (slow - soon OOO) wrote:
> this is a somewhat new behavior, because previously we'd only do this if there
> was a context disposal notification before, no?
> 
> But since we're respecting the idle hint, I think that's ok

Yes, this is different. Note that before we were just preforming a full gc when
incremental marking was stopped. However, we should do a full gc when the hint
is big enough. I thought about doing it in a separate cl but it is quit a mess.

[Hannes Payer (out of office), 2014-08-07 12:17:00]

A *dispose storm* increases jank significantly. This may happen on regular
webpages.