Forbid Oilpan GC in blink::testing::runPendingTasks

Forbid Oilpan GC in blink::testing::runPendingTasks

As webkit unittests are run outside of the message loop, tasks run in
blink::testing::runPendingTasks are executed as non-nested tasks. That means
the registered GCTaskObserver will run GC with NoHeapPointerOnStack. This is
problematic because we often have heap pointers on stack.

This change forbid Oilpan GC in runPendingTasks to avoid such a problem.

BUG=613115
Committed: https://crrev.com/0b9fcb3822616d2e067aa29192f1d4e4238db2f9
Cr-Commit-Position: refs/heads/master@{#394743}

[yhirano, 2016-05-19 11:19:43]

yhirano@chromium.org changed reviewers:
+ haraken@chromium.org

[haraken, 2016-05-19 11:25:11]

LGTM, thanks.

[yhirano, 2016-05-19 11:30:54]

The CQ bit was checked by yhirano@chromium.org

[commit-bot: I haz the power, 2016-05-19 11:31:16]

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

[commit-bot: I haz the power, 2016-05-19 12:00:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 12:02:57]

Description was changed from

==========
Forbid Oilpan GC in blink::testing::runPendingTasks

As webkit unittests are run outside of the message loop, tasks run in
blink::testing::runPendingTasks are executed as non-nested tasks. That means
the registered GCTaskObserver will run GC with NoHeapPointerOnStack. This is
problematic because we often have heap pointers on stack.

This change forbid Oilpan GC in runPendingTasks to avoid such a problem.

BUG=613115
==========

to

==========
Forbid Oilpan GC in blink::testing::runPendingTasks

As webkit unittests are run outside of the message loop, tasks run in
blink::testing::runPendingTasks are executed as non-nested tasks. That means
the registered GCTaskObserver will run GC with NoHeapPointerOnStack. This is
problematic because we often have heap pointers on stack.

This change forbid Oilpan GC in runPendingTasks to avoid such a problem.

BUG=613115

Committed: https://crrev.com/0b9fcb3822616d2e067aa29192f1d4e4238db2f9
Cr-Commit-Position: refs/heads/master@{#394743}
==========

[commit-bot: I haz the power, 2016-05-19 12:02:58]

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