[asterisk-bugs] [Asterisk 0010718]: ooh323 heap corruption every 3 days.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10718 
====================================================================== 
Reported By:                xrg
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10718
Category:                   Addons/chan_ooh323
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.11  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             09-14-2007 02:45 CDT
Last Modified:              10-14-2007 02:55 CDT
====================================================================== 
Summary:                    ooh323 heap corruption every 3 days.
Description: 
I have been experiencing a crash of asterisk every 2-3 days (given my
usage). Cores all suggest a heap corruption.

The data I collected so far shouldn't be that useful, I know. But any
suggestion you may have will be appreciated. Running with MALLOC_CHECK
should be my last resort, since the machine is a production one.
====================================================================== 

---------------------------------------------------------------------- 
 xrg - 10-14-07 02:55  
---------------------------------------------------------------------- 
ezio, FYI, it is not a matter of optimizing. With gcc, it is just if you
have the symbols available (-g option, may be on a separate ELF).

If it crashes too early, it might be a different case. In mine, it *must*
be related to h323 peer latency. Just the same binary hasn't crashed ever
since my ISP gave me good round-trip to the h323 peer. Wild guess (again)
some ooh323 timeout function, or some out-of sync reply does not clear the
objects in a sane way. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-14-07 02:55  xrg            Note Added: 0071930                          
======================================================================