Initialize the CPU usage variable.

Initialize the CPU usage variable.

I'm not sure why it's causing valgrind errors, since the IPC system should
always be writing the variable. But it's probably good practice to initialize
it anyway.

BUG=106067
TEST=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=113408

[yzshen1, 2011-12-01 22:15:43]

lgtm

[Timur Iskhodzhanov, 2011-12-02 14:53:31]

Please look at http://codereview.chromium.org/8769040/

[ulan, 2011-12-02 15:45:32]

On 2011/12/02 14:53:31, Timur Iskhodzhanov wrote:
> Please look at http://codereview.chromium.org/8769040/
The only difference between this CL and my CL (linked by Timur) is that my CL
initializes CPU usage to 100, so if the IPC system doesn't work (is it possible
at all?) we assume that CPU is not idle and do not send idle notifications.

[jam, 2011-12-02 17:06:52]

On 2011/12/02 15:45:32, ulan wrote:
> On 2011/12/02 14:53:31, Timur Iskhodzhanov wrote:
> > Please look at http://codereview.chromium.org/8769040/
> The only difference between this CL and my CL (linked by Timur) is that my CL
> initializes CPU usage to 100, so if the IPC system doesn't work (is it
possible
> at all?) we assume that CPU is not idle and do not send idle notifications.

better to set it to 0 because it's not a magic number like 100. If the IPC
doesn't work, then nothing else will. The process will be in the middle of
shutdown.

[brettw, 2011-12-02 21:38:22]

I guess I don't care either way. Feel free to check in yours.

[ulan, 2011-12-07 16:17:45]

On 2011/12/02 21:38:22, brettw wrote:
> I guess I don't care either way. Feel free to check in yours.

brettw, could you please check in your version?

John's argument convinced me that 0 is better.