CPU core pegged, via DCOMLauncher/audiodg.exe on multiple vendors' hardware, under Vista.
Were seeing several Vista machines, with widely varying sound hardware (onboard such as Sigmatel, Realtek, plus add-in like SB X-fi, Audigy etc) that are all exhibiting some odd behavior with our application -- a pegged CPU core. All have the latest driver updates from the OEMs, for whatever that's worth.
The problem is that when our process engages audio capture, a svchost process which spawns DCOMLauncher pegs a CPU core at close to 100%. If we kill audiodg.exe, this process goes back down to zero. (and obviously, audio capture stops :-). We did a little bit of chain-saw exploratory surgery, and it looked like something related to PnP was trying to fetch an OEM[xx].inf entry. Over and over again.
Essentially our application performs audio capture, and we have several different modes of capture that we can engage: legacy mmsystem, DirectShow, and WDM capture. All of the above show this symptom under some Vista machines, fine under XP.
Other sound applications don't appear to show this issue on the machines in question.
It also doesn't appear to happen on all Vista machines.
We've also turned off generic audio enhancements and (where applicable) any/all audio-vendor-specific enhancement features.
One more tidbit of info -- it seems to be most severe when the audio capture device in question is a USB webcam, including Microsoft's own LifeCam series.
Anybody have any ideas on the best way to trace this issue?
-WG
