| Summary: | ASTERISK-18765: Memory Leak in lock.h | ||||
| Reporter: | BrettH (zeero) | Labels: | |||
| Date Opened: | 2011-10-30 10:21:56 | Date Closed: | 2012-02-09 16:59:38.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | General | ||
| Versions: | 1.8.7.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | HP Proliant Server Centos 5.2 Asterisk 1.8.7.1 with ooh323c addon. | Attachments: | ( 0) asterisk-info.txt ( 1) system-meminfo.txt | ||
| Description: | Experiencing a memory leak with a new build of asterisk 1.8.7.1 Asterisk process is eventually killed by kernel init process due to high memory usage Environment consists of twenty two H323 Cisco gateways dialing into the Asterisk server every 5 minutes Asterisk consumes all memory and swap over a couple of hours.and process needs to be restarted | ||||
| Comments: | By: BrettH (zeero) 2011-10-30 10:23:32.657-0500 asterisk CLI output and system memory info. By: Matt Jordan (mjordan) 2011-12-28 12:01:49.973-0600 The build option DEBUG_THREADS is meant specifically for debugging, not for production systems. Regardless of any memory leaks, running Asterisk with this option turned on will significantly degrade performance. Per ASTERISK-18323, disabling this flag should resolve this issue. By: Matt Jordan (mjordan) 2012-02-09 16:59:33.722-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines | ||||