[asterisk-bugs] [Asterisk 0018194]: Loading chan_iax2.so allocates >100M RSS

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18194 
====================================================================== 
Reported By:                job
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18194
Category:                   Channels/chan_iax2
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-22 16:07 CDT
Last Modified:              2010-12-31 03:38 CST
====================================================================== 
Summary:                    Loading chan_iax2.so allocates >100M RSS
Description: 
The main asterisk process resident memory usage jumps over 100 MB when
loading chan_iax2.so. The configuration file iax.conf is empty.

If this is not reproducible for other people, let's compare build
environment and libraries.
====================================================================== 

---------------------------------------------------------------------- 
 (0130074) tilghman (manager) - 2010-12-31 03:38
 https://issues.asterisk.org/view.php?id=18194#c130074 
---------------------------------------------------------------------- 
If this is that big of a deal to you, perhaps you should be doing more
investigation as to the cause and possible fix.  Right now, given that it
does not lead to an actual failure condition, it is relegated to rather low
on the priority scale.  Unless you do the work yourself, it is unlikely
this issue will advance to a fix anytime soon. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-31 03:38 tilghman       Note Added: 0130074                          
======================================================================