Re: AULab 2.0.1 behavior on quit
Re: AULab 2.0.1 behavior on quit
- Subject: Re: AULab 2.0.1 behavior on quit
- From: Jeff Moore <email@hidden>
- Date: Tue, 27 Oct 2009 09:23:58 -0700
On Oct 26, 2009, at 10:44 PM, B.J. Buchalter wrote:
When I quit AULab 2.0.1 (have not checked on SL yet) with a doc open
with some AU plugins loaded, I find that AULab does not close my
plugin before the application terminates (it does close the plugin
if I close the AULab doc). This is not really very friendly as the
AU may hold some resource that is not automatically cleaned up when
the application context is terminated.
It may not be friendly, but it is the exact same situation that you
get if the process hosting your AU crashes.
Is this
(a) something that will be addressed in some future version of
AULab, and
(b) something that AU's in general are expected to deal with in
apps, or is it reasonable to expect that the AU will be closed
before the app hosting it is terminated?
It is completely unreasonable to expect that every app will always
clean-up and close your AU properly every single time. As I mentioned
above, processes crash and they do a lot of other unexpected things
too. I would argue that if your AU might leak resources in those
circumstances, then you have a serious bug in your AU.
The good news is that there are lots of ways to find out when a
process dies ranging from kill(2) and other signal-based approaches to
mach port death notifications. I've done a lot in this area, so I'd be
happy to help you figure out what works best for your AU.
--
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