Re: How is an AU supposed to close its files when it closes
Re: How is an AU supposed to close its files when it closes
- Subject: Re: How is an AU supposed to close its files when it closes
- From: Jeff Moore <email@hidden>
- Date: Sat, 16 Aug 2008 09:08:25 -0700
There's not really anything that you can do. That's just the behavior
of the system. The code in a component pretty much will never get
unloaded in practice - even if the component is fully released. So the
binary file is pretty much always open until the process exits.
On Aug 15, 2008, at 10:59 PM, Jeremy Sagan wrote:
I have been doing some coding help on an audiounit plugin and I have
noticed that it and virtually all Music Device AudioUnits leave
their executable open after the component has been closed. The one
notable exception appears to be the DLS MusicDevice. Which leads to
my question. What is a Music Device (or other AU) plug-in supposed
to do to ensure that it's executable file is closed in the host
after the component is closed?
Here is an example of a path to a fictional plugin's file left open:
/Library/Audio/Plug-Ins/Components/pluginnamehere.component/Contents/
MacOS/pluginnamehere
Note that I have been checking the files left open using Activity
Monitor's 'open files and ports' tab and I have tried this test with
AULab, my host, Metro, and AudioUnitHosting. I am running OS X
10.5.3 (in case it is OS related).
As I side not it would be great if AUVal posted nasty warnings if
files were left open.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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