[asterisk-bugs] [Asterisk 0016279]: [patch] asterisk reload causes mpg123 streams to be recreated
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Dec 2 19:44:53 CST 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16279
======================================================================
Reported By: parisioa
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 16279
Category: Resources/res_musiconhold
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: 1.6.1.10
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-11-18 18:14 CST
Last Modified: 2009-12-02 19:44 CST
======================================================================
Summary: [patch] asterisk reload causes mpg123 streams to be
recreated
Description:
Every time there is an asterisk reload all of the mpg123 streams get
re-started, and the old ones do not get removed. This causes many many
streams to build up over time, and after enough reloads with enough streams
actually causes asterisk to completely fail.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016207 [patch] asterisk keeps starting new pro...
======================================================================
----------------------------------------------------------------------
(0114631) tilghman (administrator) - 2009-12-02 19:44
https://issues.asterisk.org/view.php?id=16279#c114631
----------------------------------------------------------------------
What this actually looks like is unrelated memory corruption, probably by
the SIP channel. Let's open a new issue, and run your Asterisk under
Valgrind, as specified in doc/valgrind.txt. This should help us track down
where this memory corruption is occurring.
Issue History
Date Modified Username Field Change
======================================================================
2009-12-02 19:44 tilghman Note Added: 0114631
======================================================================
More information about the asterisk-bugs
mailing list