[asterisk-bugs] [Asterisk 0019108]: [regression] "sip prune" does not clean the relevant peer objects -> memleak
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Apr 13 08:48:25 CDT 2011
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=19108
======================================================================
Reported By: vrban
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 19108
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.4.40
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-04-12 10:58 CDT
Last Modified: 2011-04-13 08:48 CDT
======================================================================
Summary: [regression] "sip prune" does not clean the relevant
peer objects -> memleak
Description:
a "sip prune realtime peer" cmd does not delete/clean the relevant Peer
object.
So if you extensively use "sip prune" cmd with sip realtime, you have a
nice mem leak. on one of our asterisk e.g.:
asterisk -rx'sip show objects' |grep static
-= User objects: 1944 static, -359 realtime =-
-= Peer objects: 833682 static, -832764 realtime, 0 autocreate =-
so we have 833682! peer objects, but real peer number is 1944 (we prune
only the peer) so asterisk use around 500MB with this 833682 Peer objects.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2011-04-13 08:48 lmadsen Summary "sip prune" does not
clean the relevant peer objects -> memleak => [regression] "sip prune" does not
clean the relevant peer objects -> memleak
======================================================================
More information about the asterisk-bugs
mailing list