[asterisk-bugs] [Asterisk 0015973]: Huge memory consumption after few hours of load

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Sep 30 11:20:32 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15973 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15973
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.1.5 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-27 17:14 CDT
Last Modified:              2009-09-30 11:20 CDT
====================================================================== 
Summary:                    Huge memory consumption after few hours of load
Description: 
I'm doing load tests on Asterisk 1.6.1.5 and after few hours of load, it
takes 80% of ram (6GB installed), so it becomes unable to fork itself (when
using System() dialplan app), and creating core dump takes an hour. Core
dumps are in size of 9 Gigabytes.

Memory summary doesn't show anytingh of much usage:

80469516 bytes allocated (8800 in caches) in 71421 allocations

while top shows:

Mem:   6055876k total,  6009316k used,    46560k free,    19220k buffers
Swap:  4096564k total,  4096548k used,       16k free,   249980k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
15870 asterisk  10 -10 9780m 4.8g 3936 S    6 83.1 505:00.32 asterisk

====================================================================== 

---------------------------------------------------------------------- 
 (0111647) atis (reporter) - 2009-09-30 11:20
 https://issues.asterisk.org/view.php?id=15973#c111647 
---------------------------------------------------------------------- 
I managed to reproduce this memory usage under valgrind last night, however
box died completely because it run out of swap before i could finish
valgrind session.

Attached incomplete valgrind log, with the following lines grepped out:

Warning: invalid file descriptor
Use --log-fd=<number> to select an alternative log fd
WARNING: unhandled syscall: 126
Read the file README_MISSING_SYSCALL_OR_IOCTL
You may be able to write your own handler 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-30 11:20 atis           Note Added: 0111647                          
======================================================================




More information about the asterisk-bugs mailing list