Many people have run opus on small embedded devices. It may be the
case that your VLA support isn't providing enough stack. You may want
to try using the pseudostack mode which will instead put that memory
on the heap and give you better control over making sure you have
enough available.
On Tue, Jun 4, 2024 at 10:28?AM Leonid Shigris <LeonidS at riscogroup.com>
wrote:>
> Hi Timothy,
>
> Because I don't see any memory overflow, remains only any memory
corruption and for sure it happens inside the library.
>
> Has anyone managed to run this library on embedded systems such as STM32,
NXP IMXRT1060? By using opus_demo code (decoding part)?
>
>
> Pls advise,
>
> Kind Regards,
> Leonid Shigris
> RT Engineer
>
> Email: LeonidS at riscogroup.com
>
>
> -----Original Message-----
> From: opus <opus-bounces at xiph.org> On Behalf Of Timothy B.
Terriberry
> Sent: Tuesday, 4 June 2024 13:17
> To: opus at xiph.org
> Subject: Re: [opus] opus library issues
>
> [You don't often get email from tterribe at xiph.org. Learn why this is
important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Leonid Shigris wrote:
> > Is there a situation thatsilk frame corruption causes to system crash?
>
> The library is able to decode corrupt frames without crashing.
> _______________________________________________
> opus mailing list
> opus at xiph.org
> http://lists.xiph.org/mailman/listinfo/opus
> _______________________________________________
> opus mailing list
> opus at xiph.org
> http://lists.xiph.org/mailman/listinfo/opus