Re: (iOS AUv3) memory limit for AU Extensions
Re: (iOS AUv3) memory limit for AU Extensions
- Subject: Re: (iOS AUv3) memory limit for AU Extensions
- From: Lucas Goossen <email@hidden>
- Date: Fri, 27 Jul 2018 08:38:53 -0500
I think something that is not realized by many developers is that this limit is
shared by all instances of the plugin in a particular host. So this means if a
user can hit this limitation with even the most conservative memory using
plugins.
I too would love to see this fixed especially with such big dependence on
plugins on the system.
> On Jul 27, 2018, at 04:28, Bram Bos <email@hidden> wrote:
>
> For me it's mostly a matter of taking precautions. Right now I can open 35
> instances of my most demanding plugin before they all go *poof*
>
> But I don't like having a product with such a gaping boobytrap in it.
>
> Having said that, there are currently other plugins out there which are more
> sample-heavy or graphics/GUI-heavy which crap out after half a dozen
> instances. And it's reflecting badly on the entire platform (with vocal users
> concluding the system isn't ready for prime-time yet).
> From: Paul Sanders <email@hidden>
> Sent: Friday, July 27, 2018 11:20:40 AM
> To: Bram Bos; email@hidden
> Subject: Re: (iOS AUv3) memory limit for AU Extensions
>
> I guess my question would be: what are you using so much RAM for in the first
> place? Just my $.02.
>
> Also: please define 'crash'. Thanks.
>
> Paul Sanders (occasional poster).
>
>
> On 27/07/2018 10:05, Bram Bos wrote:
>
> Currently, iOS imposes a memory limit for AUv3 extensions. All combined
> instances of an AU extension should remain below a cap of 360Mb memory usage
> (on 64 bit devices).
>
> In all hosts I've tested with, crossing this limit will crash all instances
> of the extension without warning, often leading to problems like corrupted
> projects etc.
>
> - Are there any known plans to remove this 360Mb cap? Available memory has
> doubled/quadrupled since the standard was introduced, so it seems less
> necessary now.
>
> - Is there a way for either hosts or extensions to catch/prevent the crash
> from happening in the first place? Something a little more elegant than going
> down in flames 😉
>
> Thanks for any insights!
> _______________________________________________
> 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
_______________________________________________
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