unloading plugin bundles - is it a bad idea?
unloading plugin bundles - is it a bad idea?
- Subject: unloading plugin bundles - is it a bad idea?
- From: Ross Bencina <email@hidden>
- Date: Sat, 03 Nov 2012 18:07:29 +1100
Hello All,
Does anyone know whether it is usual and advisable for a plugin host to
unload a plugin's executable bundle after all plugin instances are
destroyed? In this case plugins include AudioUnit plugins and VST plugins.
I had been unloading the bundle with CFBundleUnloadExecutable when the
host was finished with the plugin. However I just came across a plugin
that crashes when I unload the bundle.
Then I found this thread on Carbon-dev where Chris Hanson says:
> In general, on Mac OS X one should consider bundle/plug-in unloading
> impossible; one cannot guarantee correctness even if the bundle
> itself does everything "right," because any underlying framework used
> by the bundle may not support unloading.
http://lists.apple.com/archives/carbon-dev/2011/Feb/msg00023.html
So I would like to know whether Mac OS X plugin hosts generally don't
unload plugin bundles.
Thank you,
Ross.
_______________________________________________
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