Oilpan: fix use of uninitialized raw pointers on the stack.

Oilpan: fix use of uninitialized raw pointers on the stack.

These are crashing on layout tests in the oilpan build. The reason is
that with oilpan these are just raw pointers and are therefore not
default initialized to null.

R=haraken@chromium.org, oilpan-reviews@chromium.org, timloh@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=180340

[zerny-chromium, 2014-08-15 07:24:07]

lgtm

[Mads Ager (chromium), 2014-08-15 07:24:18]

The CQ bit was checked by ager@chromium.org

[commit-bot: I haz the power, 2014-08-15 07:24:59]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/ager@chromium.org/473163002/1

[haraken, 2014-08-15 07:34:51]

LGTM

[sof, 2014-08-15 07:36:01]

lgtm (verified that were no other occurrences in this file.)

[Timothy Loh, 2014-08-15 07:41:32]

On 2014/08/15 07:23:23, Mads Ager (chromium) wrote:

Sorry about that, lgtm.

[Mads Ager (chromium), 2014-08-15 08:10:29]

On 2014/08/15 at 07:41:32, timloh wrote:
> On 2014/08/15 07:23:23, Mads Ager (chromium) wrote:
> 
> Sorry about that, lgtm.

No worries, this is impossible to notice because of the transition types.
Luckily it is easy to fix since we have a recognizable zap value for
uninitialized RawPtr<T>. :)

[commit-bot: I haz the power, 2014-08-15 08:35:21]

Committed patchset #1 (1) as 180340