fix "may be used uninitialized" warnings for older compilers

fix "may be used uninitialized" warnings for older compilers

This small change keeps some slightly older compilers happy (gcc 4.5).

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=236769

[Mostyn Bramley-Moore, 2013-11-20 16:52:52]

@sky: PTAL...

[sky, 2013-11-20 21:13:07]

LGTM

[commit-bot: I haz the power, 2013-11-20 21:21:27]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mostynb@opera.com/78863002/1

[commit-bot: I haz the power, 2013-11-20 22:00:00]

Retried try job too often on linux_rel for step(s) content_browsertests,
content_unittests, interactive_ui_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

[Mostyn Bramley-Moore, 2013-11-20 23:08:35]

On 2013/11/20 22:00:00, I haz the power (commit-bot) wrote:
> Retried try job too often on linux_rel for step(s) content_browsertests,
> content_unittests, interactive_ui_tests
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

Hmm, I need to poke around a bit more to figure out if it is a real problem if
BrowserThreadImpl::PostTaskHelper can't figure out what the current thread is,
or if my sanity check is simply too strict.

[Mostyn Bramley-Moore, 2013-11-22 08:35:45]

I think the win_rel failures with the current version of this patch (which only
initializes the variable, no new DCHECK) are unrelated.

@sky: does this still look good to you?

[sky, 2013-11-22 14:29:19]

LGTM

[commit-bot: I haz the power, 2013-11-22 14:30:42]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/mostynb@opera.com/78863002/410001

[commit-bot: I haz the power, 2013-11-22 15:53:41]

Change committed as 236769