| Summary: | ASTERISK-26020: memory leak | ||||
| Reporter: | Bill Neely (ceo_xantek) | Labels: | |||
| Date Opened: | 2016-05-12 13:53:11 | Date Closed: | 2020-01-14 11:13:55.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 13.8.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Asterisk 13.8.2 running on CentOS 7 * has about 200 sip accounts registered No pjsips yet | Attachments: | ( 0) debug_log_26020 | ||
| Description: | Asterisk runs out of memory after several days.
When first started, Asterisk is using 5.3% of my 1GB of memory After 16 hours uptime, Asterisk is using 13.6% of memory Getting the %'s from top Let me know if I can provide additional info | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-05-12 13:53:12.242-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Rusty Newton (rnewton) 2016-05-12 16:46:55.358-0500 Yes we'll need quite a bit more information to investigate. We really need to know what Asterisk is doing while running and more about the configuration. If you can reproduce the issue in small scale with a few phones but the same configuration - that would be most helpful. Please follow the instructions here: https://wiki.asterisk.org/wiki/display/AST/Memory+Leak+Debugging By: Bill Neely (ceo_xantek) 2016-05-12 17:36:43.446-0500 I could certainly run out some log files.How long should I run it to be useful? By: Rusty Newton (rnewton) 2016-05-12 17:51:30.689-0500 As short/small as possible to observe the issue happening. We don't need a massive example. By: Bill Neely (ceo_xantek) 2016-05-13 08:50:35.702-0500 Here is a log file. During the time the log was running, the physical memory used by process (reported by top) went from 138524 to 138600 By: Rusty Newton (rnewton) 2016-05-15 15:40:33.317-0500 One note - the MALLOC_DEBUG output needs to correlate with the debug file from the same run. We need to see the MALLOC output and see what the system was doing at the time. Thanks! By: Richard Mudgett (rmudgett) 2016-05-16 14:21:41.336-0500 This seems like ASTERISK-25905 where asterisk never gives memory back to the OS even though it has returned the memory back to the process's free heap. By: Asterisk Team (asteriskteam) 2016-06-01 12:00:01.327-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||||