Re: AU - avoiding crash when unregistering control class
Re: AU - avoiding crash when unregistering control class
- Subject: Re: AU - avoiding crash when unregistering control class
- From: Airy André <email@hidden>
- Date: Thu, 9 Jan 2003 21:00:32 +0100
Unless there is something wrong with the plugin loading part, there
should
be only one instance of the code, even if you have several instances of
the
plugin. So you should have no need to register your control with a
different
ID for every instance you load.
Then, since I think the GUI code is loaded at the same time as the DSP
part, as long
as you do not remove all of the instances of your plugin from the host,
I see
no reason why the address of your code would change. So, there should be
no risk of crash when your open the GUI window.
The only case I see where you could have a crash is if you load you
plugin,
remove it, then reload it again. Then it could be load at a different
address.
But I did not look in details to the plugin loading mechanism so I
could be
completely wrong...
Airy
Le jeudi, 9 jan 2003, ` 02:06 Europe/Paris, Marc Poirier a icrit :
Ack! Then what the heck good is it??? I'll still have to generate a
new name for the class every time in instantiate it in order to
register the control class then, right? What a bummer!
I guess that we need to no matter what because, with plugins, we could
have multiple instances running side by side. But I think that
unregistering the class, when possible, avoids some memory leakage at
least...
Marc
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.