Eagerly remove disposed DOMTimers as observers upon completion.

Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=

Committed: https://crrev.com/6ce5b24bfbde8a3fd8943a3169872022f1084d3f
Cr-Commit-Position: refs/heads/master@{#395012}

[sof, 2016-05-19 21:33:58]

sigbjornf@opera.com changed reviewers:
+ oilpan-reviews@chromium.org

[sof, 2016-05-19 21:33:59]

please take a look.

let's try this one again.

[haraken, 2016-05-19 23:41:10]

LGTM

[sof, 2016-05-20 05:21:29]

Description was changed from

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=
BUG=
==========

to

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=
==========

[sof, 2016-05-20 05:22:04]

The CQ bit was checked by sigbjornf@opera.com

[commit-bot: I haz the power, 2016-05-20 05:22:34]

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

[commit-bot: I haz the power, 2016-05-20 06:10:04]

Description was changed from

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=
==========

to

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=
==========

[commit-bot: I haz the power, 2016-05-20 06:10:05]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-05-20 06:11:11]

Description was changed from

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=
==========

to

==========
Eagerly remove disposed DOMTimers as observers upon completion.

Once the coordinator lets go of a timer, no need to keep it
around as an observer of the ExecutionContext.

The previous, reverted, attempt (r392309) detached the DOMTimer too
soon, causing DOMTimer nesting levels to grow without being reset.

R=haraken
BUG=

Committed: https://crrev.com/6ce5b24bfbde8a3fd8943a3169872022f1084d3f
Cr-Commit-Position: refs/heads/master@{#395012}
==========

[commit-bot: I haz the power, 2016-05-20 06:11:12]

Patchset 2 (id:??) landed as
https://crrev.com/6ce5b24bfbde8a3fd8943a3169872022f1084d3f
Cr-Commit-Position: refs/heads/master@{#395012}