[Home]

Summary:ASTERISK-26169: format_ogg_vorbis: Memory leak using OGG in MixMonitor
Reporter:Ivan Myalkin (scrumble)Labels:
Date Opened:2016-07-01 08:40:50Date Closed:2017-04-19 09:59:09
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_mixmonitor Formats/format_ogg_vorbis
Versions:11.7.0 11.22.0 13.1.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Linux Ubuntu 14.04.1 kernel 3.13.0-32 Linux Ubuntu 14.04.4 kernel 4.4.0-22 Asterisk running in docker containersAttachments:( 0) valgrind_ogg_long.txt
( 1) valgrind_wav_long.txt
Description:We detect a memory leak while using MixMonitor when try to record calls in .ogg.
Dialplans are checked, StopMixMonitor presents everywhere. All records are correct.
More calls - more records - more memory consumption - ~100 Mb on 300 recorded calls.
If we changes write format to wav everything is fine, memory consuption does not exceed 45 Mbytes (over 1000 calls, 50 users)
Here is Valgrind logs with ogg and wav (totally 30 calls in each case).
We also try to compile latest asterisk, libogg, libvorbis from latest sources, but proplem persists.
Comments:By: Asterisk Team (asteriskteam) 2016-07-01 08:40:51.397-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: Joshua C. Colp (jcolp) 2016-07-05 05:54:51.962-0500

Please follow the instructions on the wiki[1] for getting the needed information for a memory leak.

[1] https://wiki.asterisk.org/wiki/display/AST/Memory+Leak+Debugging

By: Asterisk Team (asteriskteam) 2016-07-19 12:00:01.299-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

By: Friendly Automation (friendly-automation) 2017-04-18 14:15:25.212-0500

Change 5476 merged by George Joseph:
format_ogg_vorbis: Clear ogg/vorbis data structures on close

[https://gerrit.asterisk.org/5476|https://gerrit.asterisk.org/5476]

By: Friendly Automation (friendly-automation) 2017-04-19 08:39:15.447-0500

Change 5475 merged by Joshua Colp:
format_ogg_vorbis: Clear ogg/vorbis data structures on close

[https://gerrit.asterisk.org/5475|https://gerrit.asterisk.org/5475]

By: Friendly Automation (friendly-automation) 2017-04-19 08:39:35.181-0500

Change 5477 merged by Joshua Colp:
format_ogg_vorbis: Clear ogg/vorbis data structures on close

[https://gerrit.asterisk.org/5477|https://gerrit.asterisk.org/5477]