Re: unloading plugin bundles - is it a bad idea?
Re: unloading plugin bundles - is it a bad idea?
- Subject: Re: unloading plugin bundles - is it a bad idea?
- From: Bastian Schnuerle <email@hidden>
- Date: Sat, 03 Nov 2012 11:39:01 +0100
hi ross,
i never unload the executable bundle, i think the host does that (if
the application is terminated?).
the only thing that is called in my plug-ins and only for old carbon
style plugins is CFBundleCloseBundleResourceMap, for Cooca nothing is
called if the instance of the plug-in gets destroyed and my plug-ins
have never crashed in that moment.
cheers,
bastian
Am 03.11.2012 um 08:07 schrieb Ross Bencina:
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:
email@hidden
This email sent to email@hidden
_______________________________________________
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