<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body bgcolor="#FFFFFF">
I got over the stack overflow issue it seems. I was using destroy() API to free the encoder or decoder instance memory. In that function, Only the structure opusEncoder is getting freed. When I used create() call to allocate memory, it used get_size() function
in which size it returned combined sizeof(struct OpusEncoder) + silkEncSizeBytes + celtEncSizeBytes. Now in destroy() I called get_size again and freed entire memory and the issue is fixed! I can turn on any number of times in real time without any issue.<br>
<br>
Thank You guys for your time! <br>
<br>
<br>
<div class="moz-signature"><style>
<!--
@font-face
        {font-family:"MS Mincho"}
@font-face
        {font-family:"\@MS Mincho"}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman"}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline}
span.SpellE
        {}
span.GramE
        {}
@page Section1
        {margin:1.0in 1.25in 1.0in 1.25in}
div.Section1
        {}
-->
</style>
<div class="Section1">
<p class="MsoNormal"><span style="font-size:9.0pt; font-family:Arial">Best Regards</span></p>
<p class="MsoNormal"><span style="font-size:9.0pt; font-family:Arial">Fezin E T <br>
<br>
<span style="color:#4D4D4D"></span></span>On 5/27/2013 8:50 PM, Jean-Marc Valin wrote:</p>
</div>
</div>
<blockquote type="cite">
<pre>Did you try replacing the create() with separate malloc() and init()
steps. If so, which of the two was causing the problems?
BTW, you need a C99 compiler for VAR_ARRAYS to work, although you may be
able to use USE_ALLOCA.
        Jean-Marc
On 05/27/2013 08:36 AM, Fezin E T wrote:
</pre>
<blockquote type="cite">
<pre>Guys,
Program stack is getting overflowed when I create and destroy encoder
instance continuously for around 30 times. How can I ensure stack is
completely freed when I destroy the encoder instance? I tried with
VAR_ARRAYS. But Its giving me errors while I try to compile. I suppose
VAR_ARRAYS allocates local variables as arrays so that they could go on
to stack and finally when we leave the function, the stack is freed.
when I use VAR_ARRAYS, I get this error " declarations may not appear
after an executable statement in the block". Is there any changes need
to be done in stack_alloc.h ? Have you guys faced same trouble or any
fix is already done on this issue?
My platform is TI C6424, CCS and windows.
--
Best Regards
Fezin E T
Senior Engineer - Systems Business Unit | Design And Development
TATA ELXSI
Technopark CampusTrivandrum 695 581 India
Tel +91 471 666 1117
_www.tataelxsi.com <a class="moz-txt-link-rfc2396E" href="http://www.tataelxsi.com/"><http://www.tataelxsi.com/></a>_
Notice: The information contained in this e-mail message and/or
attachments to it may contain confidential or privileged information. If
you are not the intended recipient, any dissemination, use, review,
distribution, printing or copying of the information contained in this
e-mail message and/or attachments to it are strictly prohibited. If you
have received this communication in error, please notify us by reply
e-mail or telephone and immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
opus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:opus@xiph.org">opus@xiph.org</a>
<a class="moz-txt-link-freetext" href="http://lists.xiph.org/mailman/listinfo/opus">http://lists.xiph.org/mailman/listinfo/opus</a>
</pre>
</blockquote>
<pre>
.
</pre>
</blockquote>
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information
contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank
you
<br clear=all>
</body>
</html>