I'm running Google Desktop 5.9.0911.03589-en-pb on a Vista Enterprise
SP2 32-bit system. Statistics collected with Sysinternals Process
Explorer and Procmon.

This morning I noticed an unusually high CPU utilization by the System
"process" (PID 4), a constant background of between 7% and 10%
utilization, coming from a thread running inside Ntkrnlpa.exe, the
windows kernel.

After some experimentation, I determined that when I exited Google
Desktop, or suspended one of the two GoogleDesktop.exe processes, the
System CPU utilization dropped to zero.  If I started Google Desktop
back up, or resumed the GoogleDesktop.exe process, it would shoot back
up as before.  Here's a screenshot of Proces Explorer:

   http://www.flickr.com/photos/44698399@N00/4460126448/sizes/l/

You can see where the CPU for the System process drops to zero
temporarily -- that's where I paused the GoogleDesktop.exe process.
You can also see the GoogleDesktop.exe thread that I think is
responsible, and the stack trace for that thread.

So what is GoogleDesktop.exe doing that's making the kernel work so
hard?  Using Procmon, I could see that this process seems to be in an
infinite loop of querying (and failing to read) two registry keys:

   HKLM\SOFTWARE\Google Desktop, and
   HKLM\SOFTWARE\Google\Google Desktop\user_user_default_lcid

It's doing this about 30 times per second.  Here's the Procmon
screenshot:

   http://www.flickr.com/photos/44698399@N00/4460126496/sizes/o/

What's going on here?  Is this a bug?

Thanks.

-David

By the way, that should be

   HKLM\SOFTWARE\Google\Google Desktop\use_user_default_lcid

and not "user_user_default_lcid".

-David