Re: HALPlugIn::Initialize appears to be freezing
Re: HALPlugIn::Initialize appears to be freezing
- Subject: Re: HALPlugIn::Initialize appears to be freezing
- From: Christopher Ashworth <email@hidden>
- Date: Thu, 12 Jul 2007 16:26:40 -0400
On Jul 12, 2007, at 3:43 PM, Jeff Moore wrote:
It looks like somebody's user-land audio driver is attempting to
open a component. This isn't something that the HAL does, so it
pretty much means that it's a third party driver. You'd need to
find out what driver it is from the user.
The odd thing is that, when I was casting about for some way to
recreate this and see it with my own eyes, I went to the local Apple
Store and wandered around plugging my test devices into their
machines and launching my app. (With permission, of course.)
It turned out that their machines were set up with two different base
images at the time--one of them would cause the freeze and the other
would not. Seems odd that the Apple Store machines would have third
party drivers on their display machines...or maybe that's not odd, I
guess I don't know what they'd put on there....
Anyway, thanks, I'll follow this lead.
Stupid question: is there any easy way to identify audio drivers in a
system profile? I've been collecting profiles of machines that
freeze, but have been unable to properly sort through the information
to look for clues; a straight diff between freezer/non-freezer
machines was too polluted to be useful.
Best,
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden